Mailing-List: contact dev-help@falcon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@falcon.apache.org
Date: Mon, 31 Aug 2015 09:53:45 +0000 (UTC)
From: "Pallavi Rao (JIRA)" <jira@apache.org>
To: dev@falcon.incubator.apache.org
Message-ID: <JIRA.12832044.1432270869000.209681.1441014825956@Atlassian.JIRA>
In-Reply-To: <JIRA.12832044.1432270869000@Atlassian.JIRA>
References: <JIRA.12832044.1432270869000@Atlassian.JIRA>
 <JIRA.12832044.1432270869727@arcas>
Subject: [jira] [Commented] (FALCON-1233) Migration from oozie coord and
 native scheduler
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Pallavi Rao commented on FALCON-1233:
-------------------------------------

1) Well, there is no update to the definition as such and the definition shouldn't contain the scheduler information either. That is why I wanted to add it to the schedule command.
2) That is right. When user moves back to native scheduler, it is similar to resume, only older instances are not resumed. Hence the new state (MOVED) to differentiate between SUSPENDED and this.
3) Agrred. But, I want to park that for the first-cut implementation.


> Migration from oozie coord and native scheduler
> -----------------------------------------------
>
>                 Key: FALCON-1233
>                 URL: https://issues.apache.org/jira/browse/FALCON-1233
>             Project: Falcon
>          Issue Type: Sub-task
>            Reporter: Pallavi Rao
>            Assignee: Pallavi Rao
>         Attachments: Migrating to Native Scheduler - Approach.pdf
>
>
> The migration should be as seamless as possible and the user should be able to migrate to the native scheduler in a phased manner.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)