falcon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel del Castillo (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FALCON-1573) Supply user-defined properties to Oozie workflows during schedule
Date Tue, 03 Nov 2015 14:53:27 GMT

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

Daniel del Castillo commented on FALCON-1573:
---------------------------------------------

Hi [~ajayyadava],

Thanks for the feedback and updating the ticket for me.

What you say sounds like a good approach indeed and [~pallavi.rao] also was under the impression
that it would work this way. I was just a little concerned about users overriding system properties
like _oozie.libpath_ but I suppose users must know what they are doing if they try to override
these values. In this scenario users could end up with entity definitions that don't match
the scheduled entities, would that be inconvenient?

Having said all this, I'm happy to make the change you suggest and provide a second version
of the patch.


> 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
>            Priority: Minor
>         Attachments: FALCON-1573-v1.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)

Mime
View raw message