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-1434) Enhance schedule API to accept key-value properties
Date Wed, 16 Sep 2015 06:57:45 GMT

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

Pallavi Rao commented on FALCON-1434:

[~sowmyaramesh], I have detailed out some of this in FALCON-1233. To summarize, for the first
release (basic version) of the native scheduler we will not allow migrating from Oozie to
native. User will have to delete and recreate (and schedule) the entity. So, user will see
an error if he attempts to change the scheduler after the entity is scheduled. However, for
subsequent releases, I believe that migration has to be seamless and we should allow user
to switch schedulers.

> Enhance schedule API to accept key-value properties
> ---------------------------------------------------
>                 Key: FALCON-1434
>                 URL: https://issues.apache.org/jira/browse/FALCON-1434
>             Project: Falcon
>          Issue Type: Sub-task
>            Reporter: Pallavi Rao
>            Assignee: Pallavi Rao
>             Fix For: trunk
>         Attachments: FALCON-1434-v2.patch, FALCON-1434.patch
> The schedule API will be enhanced to accept a key-value properties. This is a foundation
to enable users to specify the scheduler on which they want to schedule the entity. This in
turn enables migration to native scheduler from Oozie.
> Example:
> bin/falcon entity -schedule -props falcon.scheduler=native -name <entity name>

This message was sent by Atlassian JIRA

View raw message