[
https://issues.apache.org/jira/browse/OOZIE-1532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14037052#comment-14037052
]
Shwetha G S commented on OOZIE-1532:
------------------------------------
{quote}
Its depend on how do u interpret "len". For me it's number of coord action
available. It doesn't represent action number .If user knows that coord older
than (30 days) is purged and len=10 returning 10 available is also ok.
{quote}
len is relative to start. Action number really matters because depending on
when the query is fired it gives different results(other than new actions
created). Even if the users are aware of 30 day purging, they also need to know
when exactly purging runs(because of restart the schedule might have changed or
purging may not be working because of reason or may be disabled temporarily
because of some issue) to get the required results.
This is important if the user has query like get status of actions with nominal
time in some time range(this is required while monitoring a data pipeline).
Oozie doesn't expose this directly. The way we do it is by computing action
number range from coord start, frequency and the given timerange, and then use
start and len to get the required results. This won't work if get actions
returns actions relative to the data in DB.
> Purging should remove completed children job for long running coordinator jobs
> ------------------------------------------------------------------------------
>
> Key: OOZIE-1532
> URL: https://issues.apache.org/jira/browse/OOZIE-1532
> Project: Oozie
> Issue Type: New Feature
> Reporter: Srikanth Sundarrajan
> Assignee: Bowen Zhang
> Attachments: oozie-1532.patch, oozie-1532.patch
>
>
> Specifically, this is for long running coordinator jobs with high frequency.
> all child workflows are never purged as the coord job is still running.
> Oozie server configuration that indicates how many coordinator actions
> frequency ticks to keep. By doing this it would be possible to purge running
> coord jobs. By default this would not be enabled and the current logic would
> remain.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
