[
https://issues.apache.org/jira/browse/FALCON-1573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15006012#comment-15006012
]
Ajay Yadava edited comment on FALCON-1573 at 11/15/15 8:09 PM:
---------------------------------------------------------------
Namespace had never been a hard requirement, for example it didn't block
FALCON-1434. Even if we decide to have namespaces it should not be a mandatory
requirement for it to be addressed as part of this JIRA. It can, and according
to me it should, be addressed in another JIRA without needing to rewrite
current patch completely(before next release if backwards compatibility is a
concern). I believe this JIRA adds value in it's current form and should be
committed. Agreed?
was (Author: ajayyadava):
Namespace had never been a had requirement, for example it didn't block
FALCON-1434. Even if we decide to have namespace it should not be a mandatory
requirement for it to be addressed as part of this JIRA. It can, and according
to me it should, be addressed in another JIRA without needing to rewrite
current patch completely(before next release if backwards compatibility is a
concern). I believe this JIRA adds value in it's current form and should be
committed. Agreed?
> Supply user-defined properties to Oozie workflows during schedule
> -----------------------------------------------------------------
>
> Key: FALCON-1573
> URL: https://issues.apache.org/jira/browse/FALCON-1573
> Project: Falcon
> Issue Type: New Feature
> Components: oozie
> Affects Versions: trunk
> Reporter: Daniel del Castillo
> Assignee: Daniel del Castillo
> Priority: Minor
> Fix For: trunk
>
> Attachments: FALCON-1573-v1.patch, FALCON-1573-v2.patch,
> FALCON-1573-v3.patch
>
>
> The work in FALCON-1434 added the ability to specify properties for the
> purpose of enabling scheduler selection. However, this could be more
> generally useful as a means for users to submit custom properties that will
> be visible in Oozie workflows.
> This will enable users to reference properties in the entity XML itself and
> passing these properties down to workflows. For example, a process scheduled
> with the command:
> {code}
> bin/falcon entity -schedule -type process -name helloFalconProcess
> -properties custom.property:HEY
> {code}
> can reference the property _custom.property_ in the process XML as
> {code:xml}
> <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
> <process name="helloFalconProcess" xmlns="uri:falcon:process:0.1">
> ...
> <properties>
> ...
> <property name="customProperty" value="${coord:conf('custom.property')}"/>
> ...
> </properties>
> ...
> </process>
> {code}
> An Oozie workflow can then easily make use of such property:
> {code:xml}
> <workflow-app xmlns="uri:oozie:workflow:0.4" name="hello-falcon-wf">
> ...
> <java>
> ...
> <arg>--customValue=${customProperty}</arg>
> ...
> </java>
> ...
> </workflow-app>
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
