[jira] [Commented] (OOZIE-138) GH-112: Revisit Purging logic

["Hadoop QA (JIRA)" <ji...@apache.org>]

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

Hadoop QA commented on OOZIE-138:
---------------------------------

mislam77 remarked:
Two sub-issues.

Issue 1:  Which record to purge?

In oozie, we have parent-child (a.k.a. job-action) relationship among the entities

Question is:
If a parent is active, but children finished long time back. Should the child action be purged when its parent is still active.
We have to think from coordinator job/action as well as workflow job/action perspective.

To make thing further complicated, If WF action is started by a coordinator job, if the coordinator is active should we delete WF action?

In other words, when a workflow action should be purged? when a coordinator action should be purged.

Currently , we don't consider the parent status.

 
Issue 2: Record to soft/hard delete
Support the both option that could be selected through oozie-site configuration.

In hard delete option, all the eligible records will be deleted by oozie.
In soft delete mode, all eligible records will be marked as "deleted" through a column. 

Then other DB script will periodically remove those records (run outside oozie). For this, in our existing query, we will need to add condition where clause such as "deleted = false".

> GH-112: Revisit Purging logic
> -----------------------------
>
>                 Key: OOZIE-138
>                 URL: https://issues.apache.org/jira/browse/OOZIE-138
>             Project: Oozie
>          Issue Type: Bug
>            Reporter: Hadoop QA
>
> Currently purging of coordinator jobs are not correct.
> In addition, other purging logic should be re-evaluated.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira