[
https://issues.apache.org/jira/browse/FALCON-1434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14745129#comment-14745129
]
Pallavi Rao commented on FALCON-1434:
-------------------------------------
Sorry [~sowmyaramesh], I did miss those comments on RB. Let me answer them
here. This patch basically opens up possibility of user supplying params to the
scheduler (as we move away from Oozie coord and towards native scheduler, this
will be useful).
1. The properties supplied to the scheduler (as option to schedule) determine
how the entity is scheduled. For example, whether to schedule the entity on
native scheduler or Oozie coord. Currently, don't plan to allow for a change to
the way it is scheduled (as part of update). But, we can re-consider that in
the future and will file a separate JIRA if required.
2. Validation doesn't really need to be done by the validate API. Any key-value
supplied will be validated by the scheduler.
> 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
(v6.3.4#6332)
