CODEWITHSUNDEEP
clouderaooziehue
elkarel
elkarel

Reputation: 753

Externalize properties for Oozie workflows in Cloudera

we are developing dozens of different workflows in Oozie. We use 3 environments, DEV, PRE and PRO.

What I'd like to do is to keep same workflow.xml files in all 3 environments and only read properties for db connections, urls, authentications etc from the Cloudera environment. In this way, it would be possible to version control the files and deploy them easily. Is it possible?

Googling, I saw maybe config-default.xml would be a place for default property values, but I cannot find any in our Cloudera 5.10. We use Hue to design the workflows, algthough we can use other way to define WFs.

Thanks!

Upvotes: 0

Views: 299

Answers (1)

Lan
Lan

Reputation: 6660

You can use job properties to achieve this. 

oozie job -oozie http://localhost:11000/oozie -config dev.properties -run

If you set a property as queueName=devqueue in your dev.properties file, you can refer to it in the workflow.xml as ${queueName}

Please note that job properties file is a local file, not in HDFS. You can get more details about this in https://oozie.apache.org/docs/4.0.0/DG_Examples.html.

Upvotes: 1

Related Questions