From dev-return-14869-apmail-falcon-dev-archive=falcon.apache.org@falcon.apache.org Wed Sep 16 06:57:47 2015 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 8FEB217598 for ; Wed, 16 Sep 2015 06:57:47 +0000 (UTC) Received: (qmail 80835 invoked by uid 500); 16 Sep 2015 06:57:47 -0000 Delivered-To: apmail-falcon-dev-archive@falcon.apache.org Received: (qmail 80773 invoked by uid 500); 16 Sep 2015 06:57:47 -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 80537 invoked by uid 99); 16 Sep 2015 06:57:47 -0000 Received: from Unknown (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 16 Sep 2015 06:57:47 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id F18571A2041 for ; Wed, 16 Sep 2015 06:57:46 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-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-us-west.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id YT_TVWLli-6O for ; Wed, 16 Sep 2015 06:57:46 +0000 (UTC) Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx1-us-west.apache.org (ASF Mail Server at mx1-us-west.apache.org) with SMTP id 32821205B3 for ; Wed, 16 Sep 2015 06:57:46 +0000 (UTC) Received: (qmail 79879 invoked by uid 99); 16 Sep 2015 06:57:46 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 16 Sep 2015 06:57:46 +0000 Date: Wed, 16 Sep 2015 06:57:45 +0000 (UTC) From: "Pallavi Rao (JIRA)" To: dev@falcon.incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (FALCON-1434) Enhance schedule API to accept key-value properties 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-1434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14747008#comment-14747008 ] Pallavi Rao commented on FALCON-1434: ------------------------------------- [~sowmyaramesh], I have detailed out some of this in FALCON-1233. To summarize, for the first release (basic version) of the native scheduler we will not allow migrating from Oozie to native. User will have to delete and recreate (and schedule) the entity. So, user will see an error if he attempts to change the scheduler after the entity is scheduled. However, for subsequent releases, I believe that migration has to be seamless and we should allow user to switch schedulers. > Enhance schedule API to accept key-value properties > --------------------------------------------------- > > Key: FALCON-1434 > URL: https://issues.apache.org/jira/browse/FALCON-1434 > Project: Falcon > Issue Type: Sub-task > Reporter: Pallavi Rao > Assignee: Pallavi Rao > Fix For: trunk > > Attachments: FALCON-1434-v2.patch, FALCON-1434.patch > > > The schedule API will be enhanced to accept a key-value properties. This is a foundation to enable users to specify the scheduler on which they want to schedule the entity. This in turn enables migration to native scheduler from Oozie. > Example: > bin/falcon entity -schedule -props falcon.scheduler=native -name -- This message was sent by Atlassian JIRA (v6.3.4#6332)