HUE-1679 [oozie] Save a workflow with a bad name fails with no information

Review Request #3866 - Created Nov. 26, 2013 and submitted

Abraham Elmahrek
old-hue-rw
HUE-1679
hue
enricoberti, romain
commit ba13a8dbd04710b23cd8197c2babb66782dffd63
Author: Abraham Elmahrek <abraham@elmahrek.com>
Date:   Tue Nov 26 10:36:41 2013 -0800

    HUE-1679 [oozie] Save a workflow with a bad name fails with no information
    
    Added JS for workflow properties.
    Improved error handling when creating a workflow as well.

:100644 100644 cbdc2ab... 4067f28... M	apps/oozie/src/oozie/templates/editor/edit_workflow.mako
:100644 100644 64014c0... 85e1063... M	apps/oozie/src/oozie/views/editor.py
:100644 100644 411a0d8... 2194c96... M	apps/oozie/static/js/workflow.js
:100644 100644 b04d9f3... fea1644... M	apps/oozie/static/js/workflow.node.js
manual
  • 1
  • 0
  • 0
  • 1
  • 2
Description From Last Updated
should we map the exception or is it fine? Romain Rigaux
  1. Cool!
  2. we just support 400 errors?
    1. Yes. If it's a 500 error, then something unknown happened. It won't be 200, since that's not how the API is defined. It seems like an ok idea to standardize on 400 status code for request errors (or form errors) in the Oozie app.
  3. should we map the exception or is it fine?
    1. This is a fail safe... the exception is to make sure that execution of the workflow builder isn't halter.
  4. 
      
Review request changed

Status: Closed (submitted)

Loading...