[
https://issues.apache.org/jira/browse/FALCON-369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13943042#comment-13943042
]
Shwetha G S edited comment on FALCON-369 at 3/21/14 1:20 PM:
-------------------------------------------------------------
This is the first cut to review the approach. Its implemented just for process,
but gives an essence of the approach. The code is just moved from
OozieProcessWorkflowBuilder to different classes. Tested this with an end to
end flow for process with filesystem location.
If you have any suggestions/concerns, please bring it up now to avoid a lot of
re-work later.
was (Author: shwethags):
This is the first cut to review the approach. Its implemented just for process,
but gives an essence of the approach. The code is just moved from
OozieProcessWorkflowBuilder to different classes. Tested this with an end to
end flow for process with filesystem location.
If you have any suggestions/concerns, please bring it up now.
> Refactor workflow builder
> -------------------------
>
> Key: FALCON-369
> URL: https://issues.apache.org/jira/browse/FALCON-369
> Project: Falcon
> Issue Type: Improvement
> Reporter: Shwetha G S
> Assignee: Shwetha G S
> Attachments: FALCON-369.patch
>
>
> Currently, feed/process workflow builder is a single class which handles all
> different cases of lifecycles, storage types, workflow engines and building
> all oozie entities(workflow, coord and bundle). This is not readable and
> difficult to maintain. This needs some re-factoring.
> Approach:
> Maintain different builders for
> 1. oozie entities - workflow, coord and bundle.
> 2. entity types - feed and process
> 3. lifecycle - process, retention and replication
> 4. workflow engines - oozie, pig and hive
--
This message was sent by Atlassian JIRA
(v6.2#6252)
