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) Support co-existence of Oozie scheduler (coord) and Falcon native scheduler
Date Wed, 04 Nov 2015 06:26:27 GMT

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

Pallavi Rao commented on FALCON-1233:

[~pavan kumar], I have outlined the approach in the document attached to this JIRA. For the
first (or initial few) versions of the native scheduler, user will have to delete the entity
and schedule it on the native scheduler and vice-versa. But, I do understand the need to make
it even more seamless and we'll go that route eventually.

> Support co-existence of Oozie scheduler (coord) and Falcon 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-v1.patch, 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

View raw message