[
https://issues.apache.org/jira/browse/FALCON-991?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14395579#comment-14395579
]
Srikanth Sundarrajan commented on FALCON-991:
---------------------------------------------
{code}
+ coordJob = client.getCoordJobInfo(coord.getId(),
"nominaltime>=" + start + ";nominaltime<" + end,
+ 0, 1000);
{code}
Is there a fear of being stuck in the first 1000 instances when the time period
in consideration is large and frequency is small ?
> consolidate get coord actions in OozieWorkflowEngine
> ----------------------------------------------------
>
> Key: FALCON-991
> URL: https://issues.apache.org/jira/browse/FALCON-991
> Project: Falcon
> Issue Type: Improvement
> Reporter: Shwetha G S
> Assignee: Ajay Yadava
> Attachments: FALCON-991.patch
>
>
> OozieWorkflowEngine.getCoordActions() gets instances by calling
> oozieclient.getCoordAction() for each action. Its not efficient to call oozie
> API for each instance. Instead, doSummaryJobAction() gets all instances in
> bulk using oozieclient.getCoordJobInfo(). But this uses offset which won't
> work with purging of coord actions. A new API was added in oozie to get coord
> actions between timestamps. We should use that for both usecases
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
