[jira] [Commented] (FALCON-1233) Support co-existence of Oozie scheduler (coord) and Falcon native scheduler

["pavan kumar kolamuri (JIRA)" <ji...@apache.org>]

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

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

[~pallavi.rao]  I like the idea of migrating entities one by one. To move to native scheduler for an entity , should we have to stop that entity and scheduled with new start time since update is not supported ?  Can we still use Falcon API's and see the history of instances for that entity if it is migrated ? 

> Support co-existence of Oozie scheduler (coord) and Falcon 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
>             Fix For: trunk
>
>         Attachments: FALCON-1233-v1.patch, FALCON-1233.patch, Migrating to Native Scheduler - Approach v2.pdf, 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)