[
https://issues.apache.org/jira/browse/FALCON-1170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14534016#comment-14534016
]
Pallavi Rao commented on FALCON-1170:
-------------------------------------
Will refactor the builder code as follows:
1. Generate a config-default.xml along with workflow.xml whenever a workflow is
built. The default config file will have most of the configurations set in it.
Note that the config values can be overridden during run/re-run using
job.properties.
2. Move all workflow related configuration to config-default.xml and keep only
coord related variables (input, output, timestamp, startTime, endTime,
frequency) in the coordinator.xml
3. Make bundle.xml really lean. Only app path, entity name and path will be set
there.
These changes will not regress or introduce functionalities. It only enables
submission of workflows when we have a native scheduler.
> 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
>
> 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)
