[
https://issues.apache.org/jira/browse/FALCON-1233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15015241#comment-15015241
]
Ajay Yadava commented on FALCON-1233:
-------------------------------------
[~pallavi.rao]
What is the plan after the transition period? Will we always support both oozie
and native scheduler or the plan is to deprecate oozie after a while and move
completely to native scheduler?
Also, I think instead of providing property like primary and secondary and
lookup from startup.properties the value of primary and secondary we should
switch to explicitly specifying *native* and *oozie* scheduler engine for the
following reasons.
1. Primary and secondary have a notion of priority which will shift with time
in favour of the native scheduler(currently secondary).
2. Saying schedule on native or oozie is much better and explicit expression of
the intent of the user. Otherwise users will always have to check
startup.properties as which is which.
My 2 cents.
> 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)
