falcon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Srikanth Sundarrajan (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FALCON-1170) Falcon Native Scheduler - Refactor existing workflow/coord/bundle builder
Date Thu, 02 Jul 2015 08:19:04 GMT

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

Srikanth Sundarrajan commented on FALCON-1170:
----------------------------------------------

Most of the changes, from my observation are relating to moving code from CoordBuilder to
WorkflowBuilder. Looks good to me largely. A comment or two on review board.

> 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
>             Fix For: 0.7
>
>         Attachments: FALCON-1170-v2.patch, FALCON-1170.patch
>
>
> 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)

Mime
View raw message