[
https://issues.apache.org/jira/browse/OOZIE-2062?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14224489#comment-14224489
]
Jaydeep Vishwakarma commented on OOZIE-2062:
--------------------------------------------
I am also planning to add frequency based purging.
Let say if your job is running minutely. It will add more number of rows in DB
compare to other frequency jobs. Deprecation of those rows are more frequent
than other jobs. So purging logic should be different for minutely jobs.
Planning to divide purging on following category
Default
Daily
Hourly
Minutely
By default all will have same number of days. I will keep it by default to 100
days.
Frequency based purging will only work for workflow action, workflow and coord
action.
> Provide alternate purging logic
> -------------------------------
>
> Key: OOZIE-2062
> URL: https://issues.apache.org/jira/browse/OOZIE-2062
> Project: Oozie
> Issue Type: Improvement
> Reporter: Shwetha G S
> Assignee: Jaydeep Vishwakarma
>
> Currently, purge service deletes a workflow only if all its children are
> complete, coord action only if the corresponding workflow and its
> sub-workflows are complete. This logic is complicated and takes longer to
> run. Instead, provide an alternative purging logic that deleted all workflows
> whose end time is older than configured time, delete coord actions whose end
> time is older than configured time and so on. The purging logic to be used
> can be configured from oozie-site (by default can default to the current
> logic for backward compatbility)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
