[ 
https://issues.apache.org/jira/browse/OOZIE-708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alejandro Abdelnur reopened OOZIE-708:
--------------------------------------


This JIRA has not been +1. In addition, it breaks compatibility in the DB 
within 3.x releases. We should revert it.
                
> 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

        

Reply via email to