[
https://issues.apache.org/jira/browse/FALCON-369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14019631#comment-14019631
]
Shwetha G S commented on FALCON-369:
------------------------------------
Agree with the approach. The refactoring already solves some of these:
1. Builders for different oozie entities are already separated out as
OozieCoordinatorBuilder, OozieWorkflowBuilder, and OozieBundleBuilder
2. There is separate builder for different engines of process - oozie, pig and
hive
I will work on separating out builder from workflow engine so that entity
manager can build the workflow and call schedule on workflow engine. I will
create a sub-task for adding lifecycle
> 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, FalconWorkflowBuilder.png
>
>
> 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)
