[
https://issues.apache.org/jira/browse/FALCON-1591?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14994112#comment-14994112
]
Ajay Yadava edited comment on FALCON-1591 at 11/6/15 6:09 PM:
--------------------------------------------------------------
Another option is to create a new REST endpoint for a POST request with
properties file, no query params, only file submission like submit command. For
CLI we can check if the properties are in key value style or represent a file
path and call appropriate rest endpoint accordingly. This way users don't have
to learn different options or merging rules.
was (Author: ajayyadava):
One option is to create a new REST endpoint for a POST request with properties
file, no query params, only file submission like submit command. For CLI we can
check if the properties are in key value style or represent a file path and
call appropriate rest endpoint accordingly. This way users don't have to learn
different options or merging rules.
> Allow users to use a properties file when entities are scheduled
> ----------------------------------------------------------------
>
> Key: FALCON-1591
> URL: https://issues.apache.org/jira/browse/FALCON-1591
> Project: Falcon
> Issue Type: Improvement
> Components: oozie
> Affects Versions: trunk
> Reporter: Daniel del Castillo
> Priority: Minor
>
> The _schedule_ command now accepts a _properties_ option where users can pass
> properties formatted as
> {code}
> key1:val1,key2:val2,...,keyN:valN
> {code}
> For a large number of properties this is too verbose and requires a lot of
> typing.
> This ticket is to provide the same functionality as the _properties_ option
> using a text file to provide the key-value pairs in standard Java properties
> file format.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
