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-1233) Migration from oozie coord and native scheduler
Date Fri, 25 Sep 2015 06:18:04 GMT

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

Srikanth Sundarrajan commented on FALCON-1233:
----------------------------------------------

[~pallavi.rao], Can this be achieved more simply via 

{code}
    public static AbstractWorkflowEngine getWorkflowEngine(Entity entity) throws FalconException

{code}
against
{code}
    public static AbstractWorkflowEngine getWorkflowEngine() throws FalconException 
{code}

Or am I missing something that the aspect based patch is addressing ?

> Migration from oozie coord and native scheduler
> -----------------------------------------------
>
>                 Key: FALCON-1233
>                 URL: https://issues.apache.org/jira/browse/FALCON-1233
>             Project: Falcon
>          Issue Type: Sub-task
>            Reporter: Pallavi Rao
>            Assignee: Pallavi Rao
>             Fix For: trunk
>
>         Attachments: FALCON-1233.patch, Migrating to Native Scheduler - Approach v2.pdf,
Migrating to Native Scheduler - Approach.pdf
>
>
> The migration should be as seamless as possible and the user should be able to migrate
to the native scheduler in a phased manner.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message