falcon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sowmya Ramesh (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FALCON-1434) Enhance schedule API to accept key-value properties
Date Tue, 15 Sep 2015 05:59:46 GMT

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

Sowmya Ramesh commented on FALCON-1434:

[~pallavi.rao]: I have couple of queries which was added in RB. I think you missed it

1> key-value properties - Is it not required to allow this for already scheduled entities?
i.e. should be allowed for update operation too
2> Does any property passed in key-value properties requires validation? Was wondering
if it is required for validate API

> 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