falcon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Shaik Idris Ali (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FALCON-356) Merge OozieProcessMapper and OozieProcessWorkflowBuilder
Date Tue, 18 Mar 2014 06:30:47 GMT

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

Shaik Idris Ali commented on FALCON-356:
----------------------------------------

Idea warning for performance:
In OozieWorkflowEngine, it can be:  
      Map<String, Properties> newFlows = builder.newWorkflowSchedule(schedClusters.toArray(new
String[schedClusters.size()]));

+1, looks fine otherwise.

> Merge OozieProcessMapper and OozieProcessWorkflowBuilder
> --------------------------------------------------------
>
>                 Key: FALCON-356
>                 URL: https://issues.apache.org/jira/browse/FALCON-356
>             Project: Falcon
>          Issue Type: Improvement
>            Reporter: Shwetha G S
>            Assignee: Shwetha G S
>             Fix For: 0.5
>
>         Attachments: FALCON-356.patch
>
>
> There is one to one mapping between OozieProcessMapper and OozieProcessWorkflowBuilder.
Entity to oozie workflow mapping is spread across these two classes. Same goes for OozieFeedMapper
and OozieFeedWorkflowBuilder



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message