You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@falcon.apache.org by "Shwetha G S (JIRA)" <ji...@apache.org> on 2014/03/21 14:20:43 UTC

[jira] [Comment Edited] (FALCON-369) Refactor workflow builder

    [ https://issues.apache.org/jira/browse/FALCON-369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13943045#comment-13943045 ] 

Shwetha G S edited comment on FALCON-369 at 3/21/14 1:20 PM:
-------------------------------------------------------------

Known pending tasks:
1. Move the testcases
2. Move process builders to process module
3. Remove old code



was (Author: shwethags):
Known pending tasks:
1. Move the testcases
2. Move process builders to process module


> 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)