[
https://issues.apache.org/jira/browse/FALCON-1233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15024323#comment-15024323
]
Pallavi Rao commented on FALCON-1233:
-------------------------------------
[~ajayyadava], [~peeyushb], agree that the notion of primary and secondary can
be confusing especially, when user (who is different from admin) has not looked
at what is specified in startup.properties. So, I will make changes so users
can explicitly specify 'native' or 'oozie' as an option.
To maintain backward compatibility, the Factory will default to the workflow
engine specified in startup.properties, when 'native' is not specified (which
currently is OozieWorkflowEngine). The idea is that users will migrate to
native scheduler and eventually we can deprecate Oozie scheduler. At that
point, the workflow engine in startup.properties can be changed to
FalconWorkflowEngine.
Fine?
> 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)
