[
https://issues.apache.org/jira/browse/FALCON-1591?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14993472#comment-14993472
]
Daniel del Castillo commented on FALCON-1591:
---------------------------------------------
[~pallavi.rao] [~ajayyadava] I'd like to know your point of view of this should
work and quickly discuss the options:
# Reuse _properties_ parameters: if the string provided in the _properties_
option can be converted into a URI then read properties from that URI,
otherwise try to parse it as it's currently done.
# Add a new _propertiesfile_ parameter: separates the 2 things, the value of
the option must be a valid URI. Properties will have to be merged in both
_properties_ and _propertiesfile_ are set in the command.
My understanding is the REST API should mirror all the functionalities of the
CLI command. If this is the case the file must be read on the server side which
I think may be confusing to command line users.
Please let me know your thoughts.
> 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)
