You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@oozie.apache.org by "Virag Kothari (JIRA)" <ji...@apache.org> on 2012/08/03 19:57:02 UTC

[jira] [Commented] (OOZIE-708) Update the parent entity status dynamically

    [ https://issues.apache.org/jira/browse/OOZIE-708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13428263#comment-13428263 ] 

Virag Kothari commented on OOZIE-708:
-------------------------------------

Alejandro,
Its already +1 ed on review board by Mohammad (https://reviews.apache.org/r/5784/).
I had already addressed your comments about backward compatibility. By default the feature will be turned off not to break backward compatibility. So we can have it in 3.x


                
> Update the parent entity status dynamically 
> --------------------------------------------
>
>                 Key: OOZIE-708
>                 URL: https://issues.apache.org/jira/browse/OOZIE-708
>             Project: Oozie
>          Issue Type: Bug
>            Reporter: Virag Kothari
>            Assignee: Virag Kothari
>             Fix For: trunk
>
>         Attachments: OOZIE-708.diff, OOZIE-708v1.patch, Oozie state transitions.xlsx, state_transition.png
>
>
> Currently the coordinator jobs and bundles do not change their status from RUNNING even when some of the actions have failed. This jira proposes to change states from RUNNING to  RUNNING_WITH_ERROR whenever some action is failed but the job is still in in RUNNING mode. Similarly, new states like SUSPENDED_WITH_ERROR and PAUSED_WITH_ERROR also needs to be introduced

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira