[
https://issues.apache.org/jira/browse/FALCON-1170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14624367#comment-14624367
]
Ajay Yadava commented on FALCON-1170:
-------------------------------------
+1 Will commit shortly.
> Falcon Native Scheduler - Refactor existing workflow/coord/bundle builder
> -------------------------------------------------------------------------
>
> Key: FALCON-1170
> URL: https://issues.apache.org/jira/browse/FALCON-1170
> Project: Falcon
> Issue Type: Sub-task
> Reporter: Pallavi Rao
> Assignee: Pallavi Rao
> Fix For: 0.7
>
> Attachments: FALCON-1170-v2.patch, FALCON-1170-v3.patch,
> FALCON-1170.patch
>
>
> The current set of builders assume that a bundle is going to be submitted to
> Oozie, and hence, populate configuration properties at the coord level.
> When a native scheduler is built out, we will submitting workflows to Oozie
> (not coords/bundles) as the scheduling of the workflows will be done within
> Falcon.
> The existing code needs to be refactored to allow for building/submission of
> workflows too. Basically, the builders should allow for building either
> workflow/coord/bundle independently and not make assumptions that only
> bundles/coords will be submitted.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
