falcon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pallavi Rao (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FALCON-1233) Migration from oozie coord and native scheduler
Date Mon, 31 Aug 2015 09:53:45 GMT

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

Pallavi Rao commented on FALCON-1233:

1) Well, there is no update to the definition as such and the definition shouldn't contain
the scheduler information either. That is why I wanted to add it to the schedule command.
2) That is right. When user moves back to native scheduler, it is similar to resume, only
older instances are not resumed. Hence the new state (MOVED) to differentiate between SUSPENDED
and this.
3) Agrred. But, I want to park that for the first-cut implementation.

> 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
>         Attachments: 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

View raw message