falcon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ajay Yadava (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FALCON-1573) Supply user-defined properties to Oozie workflows during schedule
Date Thu, 05 Nov 2015 09:02:27 GMT

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

Ajay Yadava commented on FALCON-1573:

I am actually _very reluctant_ to have many and verbose namespaces, so I like "falcon."(the
way you have implemented the existing property for scheduler) much more instead of "falcon.system"
and no namespace for user properties. I have seen too many users crib about every extra character
that they have to type on command line and use alias instead. I also think it is much clearer
in understanding and implementing only two types of properties. Properties which are interpreted
and consumed by falcon and everything else. I am also not sure of the impact on other systems
like oozie with properties like "oozie.*" 

What I am proposing might not be best approach and if you still disagree then I am happy to
have a detailed and broader discussion (may be a DISCUSS thread) and hear thoughts and use
cases from everyone on the same but I would really like to unblock this JIRA in the meantime.
If we decide otherwise we anyhow have to fix the existing property and we will fix these new
properties along with them before next release to avoid any backward incompatibility issues.

> 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
> 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

View raw message