Description
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:
bin/falcon entity -schedule -type process -name helloFalconProcess -properties custom.property:HEY
can reference the property custom.property in the process XML as
<?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>
An Oozie workflow can then easily make use of such property:
<workflow-app xmlns="uri:oozie:workflow:0.4" name="hello-falcon-wf"> ... <java> ... <arg>--customValue=${customProperty}</arg> ... </java> ... </workflow-app>
Attachments
Attachments
Issue Links
- is related to
-
FALCON-1434 Enhance schedule API to accept key-value properties
- Resolved
- relates to
-
FALCON-1591 Allow users to use a properties file when entities are scheduled
- Open
- links to