falcon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "pavan kumar kolamuri (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FALCON-991) consolidate get coord actions in OozieWorkflowEngine
Date Mon, 21 Dec 2015 18:07:46 GMT

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

pavan kumar kolamuri commented on FALCON-991:
---------------------------------------------

[~nperiwal]  Can you please fix these test cases and resubmit the patch, this was pending
from long time.

> 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: Narayan Periwal
>         Attachments: FALCON-991-v1.patch, FALCON-991-v2.patch, FALCON-991-v3.patch, FALCON-991-v4.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)

Mime
View raw message