You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@falcon.apache.org by "Peeyush Bishnoi (JIRA)" <ji...@apache.org> on 2015/09/10 11:25:46 UTC
[jira] [Commented] (FALCON-1434) Enhance schedule API to accept
key-value properties
[ https://issues.apache.org/jira/browse/FALCON-1434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14738477#comment-14738477 ]
Peeyush Bishnoi commented on FALCON-1434:
-----------------------------------------
[~pallavi.rao] What will be the order of preference, if user has specified the key-value property through "-props" option on command line and same key-value property through Entity properties as well.
> 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.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
(v6.3.4#6332)