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 3567F188DE for ; Tue, 22 Dec 2015 10:07:50 +0000 (UTC) Received: (qmail 21800 invoked by uid 500); 22 Dec 2015 10:07:50 -0000 Delivered-To: apmail-falcon-dev-archive@falcon.apache.org Received: (qmail 21769 invoked by uid 500); 22 Dec 2015 10:07:50 -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 21758 invoked by uid 99); 22 Dec 2015 10:07:50 -0000 Received: from Unknown (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 22 Dec 2015 10:07:50 +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 96F1EC06B9 for ; Tue, 22 Dec 2015 10:07:49 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 0.426 X-Spam-Level: X-Spam-Status: No, score=0.426 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.554] 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 coJVsVDopnP6 for ; Tue, 22 Dec 2015 10:07:49 +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 BE115203BC for ; Tue, 22 Dec 2015 10:07:47 +0000 (UTC) Received: (qmail 21555 invoked by uid 99); 22 Dec 2015 10:07:46 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 22 Dec 2015 10:07:46 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 9D6772C1F54 for ; Tue, 22 Dec 2015 10:07:46 +0000 (UTC) Date: Tue, 22 Dec 2015 10:07:46 +0000 (UTC) From: "Pallavi Rao (JIRA)" To: dev@falcon.incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Assigned] (FALCON-1679) API to get type of scheduler(native/oozie) 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-1679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pallavi Rao reassigned FALCON-1679: ----------------------------------- Assignee: Pallavi Rao > API to get type of scheduler(native/oozie) > ------------------------------------------ > > Key: FALCON-1679 > URL: https://issues.apache.org/jira/browse/FALCON-1679 > Project: Falcon > Issue Type: Improvement > Components: scheduler > Affects Versions: 0.9 > Environment: QA > Reporter: Pragya Mittal > Assignee: Pallavi Rao > > With 0.9 there will be two options to schedule entity : > - Native scheduler > - Oozie > As of now there is no way to know which scheduler scheduled which entity. There should be a separate api to reflect this or we can add it in existing api. -- This message was sent by Atlassian JIRA (v6.3.4#6332)