Return-Path: X-Original-To: apmail-falcon-dev-archive@minotaur.apache.org Delivered-To: apmail-falcon-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 7EFC318EB3 for ; Tue, 22 Sep 2015 06:37:07 +0000 (UTC) Received: (qmail 34501 invoked by uid 500); 22 Sep 2015 06:37:07 -0000 Delivered-To: apmail-falcon-dev-archive@falcon.apache.org Received: (qmail 34453 invoked by uid 500); 22 Sep 2015 06:37:07 -0000 Mailing-List: contact dev-help@falcon.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@falcon.apache.org Delivered-To: mailing list dev@falcon.apache.org Received: (qmail 34442 invoked by uid 99); 22 Sep 2015 06:37:07 -0000 Received: from Unknown (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 22 Sep 2015 06:37:07 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id E9512C0252 for ; Tue, 22 Sep 2015 06:37:06 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 0.974 X-Spam-Level: X-Spam-Status: No, score=0.974 tagged_above=-999 required=6.31 tests=[KAM_LAZY_DOMAIN_SECURITY=1, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.006] autolearn=disabled Received: from mx1-eu-west.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id ADtChajMdEeb for ; Tue, 22 Sep 2015 06:37:06 +0000 (UTC) Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx1-eu-west.apache.org (ASF Mail Server at mx1-eu-west.apache.org) with SMTP id 4F6E02039F for ; Tue, 22 Sep 2015 06:37:05 +0000 (UTC) Received: (qmail 34419 invoked by uid 99); 22 Sep 2015 06:37:04 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 22 Sep 2015 06:37:04 +0000 Date: Tue, 22 Sep 2015 06:37:04 +0000 (UTC) From: "Narayan Periwal (JIRA)" To: dev@falcon.incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Assigned] (FALCON-991) consolidate get coord actions in OozieWorkflowEngine MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/FALCON-991?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Narayan Periwal reassigned FALCON-991: -------------------------------------- Assignee: Narayan Periwal (was: Ajay Yadava) > 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.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)