You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@falcon.apache.org by "Srikanth Sundarrajan (JIRA)" <ji...@apache.org> on 2015/09/04 10:51:45 UTC
[jira] [Commented] (FALCON-1233) Migration from oozie coord and
native scheduler
[ https://issues.apache.org/jira/browse/FALCON-1233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14730529#comment-14730529 ]
Srikanth Sundarrajan commented on FALCON-1233:
----------------------------------------------
Had an offline conversation with [~pallavi.rao] on this. Putting down here for reference and feedback
1. Might be useful to avoid the command line switch, as it might have shorter shelf life. Consider adding a -properties switch to support for this and future use cases
2. Defer the effort on building for migrating back and forth scheduler options. Re-evaluate position if it becomes operationally untenable
> 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)