[
https://issues.apache.org/jira/browse/FALCON-1233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14723266#comment-14723266
]
pavan kumar kolamuri commented on FALCON-1233:
----------------------------------------------
1) Migration should be done through update api right ?
2) When reverting from falcon-scheduler to oozie , we are suspending(moving)
process right ? When we are resuming back again to scheduler , we should make
sure not running old instances and running new instances in scheduler should
start from coordinator end time in oozie.
3) If user queries on status or any other API shouldn't we collect info from
both and consolidate ?
> 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)
