Mailing-List: contact dev-help@falcon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@falcon.apache.org
Date: Wed, 4 Nov 2015 10:34:27 +0000 (UTC)
From: "Daniel del Castillo (JIRA)" <jira@apache.org>
To: dev@falcon.incubator.apache.org
Message-ID: <JIRA.12908857.1446115125000.148864.1446633267761@Atlassian.JIRA>
In-Reply-To: <JIRA.12908857.1446115125000@Atlassian.JIRA>
References: <JIRA.12908857.1446115125000@Atlassian.JIRA>
 <JIRA.12908857.1446115125674@arcas>
Subject: [jira] [Commented] (FALCON-1573) Supply user-defined properties to
 Oozie workflows during schedule
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

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

I totally agree with your previous comment [~pallavi.rao], if there is a way to differentiate between what users define and what Falcon sets to do its job then this change could work as you guys initially thought and we can keep it simple. If the dev team have been thinking of introducing namespaces this could potentially be a good time to do that. What are your thoughts about this [~ajayyadava] ?

I can only find one issue related to namespaces ([FALCON-1308|https://issues.apache.org/jira/browse/FALCON-1308])

If you both agree to the introduction of namespaces then I'll raise one more ticket to do this so we can put some ideas together.

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