[
https://issues.apache.org/jira/browse/OOZIE-1449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13708822#comment-13708822
]
Robert Kanter commented on OOZIE-1449:
--------------------------------------
The 4 lines that are too long are @namedQuery changes, so that's not a problem.
The 2 test errors are unrelated (SLA stuff)
> Coordinator Workflow parent relationship is broken for purge service
> --------------------------------------------------------------------
>
> Key: OOZIE-1449
> URL: https://issues.apache.org/jira/browse/OOZIE-1449
> Project: Oozie
> Issue Type: Bug
> Components: core
> Affects Versions: trunk
> Reporter: Robert Kanter
> Assignee: Robert Kanter
> Priority: Critical
> Fix For: trunk
>
> Attachments: OOZIE-1449.patch, OOZIE-1449.patch, OOZIE-1449.patch,
> OOZIE-1449.patch
>
>
> OOZIE-1118 improved the logic of the purge service to take into account the
> parent-child relationships of bundle, coordinator, workflow, and subworkflow
> jobs. However, in queries (and test code) dealing with the coordinator
> parent of a workflow, it is incorrectly using the coordinator job id instead
> of the coordinator action id.
> This means that the purging logic won't properly associate workflows with
> their parent coordinators; all jobs should eventually be purged, so its not
> completely broken, but it is currently possible for child workflows to be
> purged before their coordinator parents (the correct behavior is for no child
> or parent to be purged until the parent and all children are ready).
> This doesn't affect the coordinator-bundle or subworkflow-workflow
> relationships because they use their parent is the job id not the action id;
> only the workflow-coordinator relationship uses the coordinator action id as
> the parent id for the workflow job.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
