Our Community is getting an upgrade! To get everything ready for the relaunch, we’ll be placing the site in read-only mode starting September 21st.
We really appreciate your understanding while we get things set up behind the scenes. Catch up on all the exciting details about the move here.
Need help or have questions? Drop us a line at [email protected]

Archives of Support Questions (Read Only)

This is an archived board for historical reference. Information and links may no longer be available or relevant
Announcements
This board is archived and read-only for historical reference. To ask a new question, please post a new topic on the appropriate active board.

How many job.properties per workflow, coordinator and bundle for Oozie?

avatar
Rising Star

Hello all,

I have around 20 workflows with a lot of dependencies between them. Can I have one job.properties for 20 Workflows?

How about coordinator and bundle? Should I use the same job.properties?

Or Do I need to have job.properties for each Workflow, each Coordinator and Bundle?

for example :

/bundle.xml

/job.properties (for bundle properties)

/workflowA

/coordinator.xml

/workflow.xml

/job.properties

/workflowB

/coordinator.xml

/workflow.xml

/job.properties

Please give me advise.

Thanks

1 ACCEPTED SOLUTION

avatar
Guru

job.properties only contains properties to be propagated to your workflows, so small answer is yes you can have a single job.properties for your 20 workflows.

Bundle and coordinators requires other parameters (like start/endDate) so it's better to have a specific job.properties for them

View solution in original post

1 REPLY 1

avatar
Guru

job.properties only contains properties to be propagated to your workflows, so small answer is yes you can have a single job.properties for your 20 workflows.

Bundle and coordinators requires other parameters (like start/endDate) so it's better to have a specific job.properties for them