You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@falcon.apache.org by "Ajay Yadava (JIRA)" <ji...@apache.org> on 2015/08/28 14:12:47 UTC

[jira] [Updated] (FALCON-991) consolidate get coord actions in OozieWorkflowEngine

     [ https://issues.apache.org/jira/browse/FALCON-991?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ajay Yadava updated FALCON-991:
-------------------------------
    Fix Version/s:     (was: 0.7)

> 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-v1.patch, FALCON-991-v2.patch, FALCON-991-v3.patch, 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)