[
https://issues.apache.org/jira/browse/FALCON-1233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14966570#comment-14966570
]
Pallavi Rao commented on FALCON-1233:
-------------------------------------
Can be done too. Guess I was just trying to avoid modifying the code base to
accommodate the native scheduler. There are places where we reuse an instance
of WorkflowEngine (rightfully so), that will need to be changed to retrieve the
instance from the factory for every call.
I can go this route too. Just a matter of moving the logic in aspect to the
Factory.
> 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
> Fix For: trunk
>
> Attachments: 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)
