[ https://issues.apache.org/jira/browse/OOZIE-2187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14579808#comment-14579808 ]
Narayan Periwal commented on OOZIE-2187: ---------------------------------------- Hi [~rkanter], While making the patch, don't use --no-prefix. The review board accepts patch with prefix. So, to create the patch to upload in review board, the example is git diff --cached > OOZIE-2251-v5.patch This should work!! > Add a way to specify a default JT/RM and NN > ------------------------------------------- > > Key: OOZIE-2187 > URL: https://issues.apache.org/jira/browse/OOZIE-2187 > Project: Oozie > Issue Type: New Feature > Components: core > Reporter: Robert Kanter > Assignee: Robert Kanter > Attachments: OOZIE-2187.patch, OOZIE-2187.patch > > > Oozie is cluster agnostic, which is why we require an RM/JT and NN per action > in your workflow (or once via the <global> section). In practice, many users > use one Oozie server per cluster, so it's an extra burden for them to have to > specify this all the time. It would be convenient if we added configuration > properties to oozie-site that would let you specify a default RM/JT and NN to > use. > This way, these users could completely omit the {{<job-tracker>}} and > {{<name-node>}} fields from their workflows; as an added benefit, they can > easily update these values if they ever rename/move their RM/JT or NN. We'd > of course still allow specifying {{<job-tracker>}} and {{<name-node>}} in > each action and {{<global>}} to allow individual workflows or actions to > override the default. -- This message was sent by Atlassian JIRA (v6.3.4#6332)