Hi Shawn, Part of the answer: For common configurations, you can include other config files into A) each workflow's and/or B)each action's config . Please see : 1)http://oozie.apache.org/docs/3.3.1/WorkflowFunctionalSpec.html#a19_Global_Configurations 2)http://oozie.apache.org/docs/3.3.1/WorkflowFunctionalSpec.html#a3.2.2_Map-Reduce_Action 3) https://cwiki.apache.org/confluence/display/OOZIE/Map+Reduce+Cookbook
Waiting others to respond the rest of you questions. Regards, Mohammad ________________________________ From: Shawn Hermans <[email protected]> To: [email protected] Sent: Wednesday, February 13, 2013 12:39 PM Subject: Configuration Managing Oozie Jobs All, I am trying to find out if there are some best practices when it comes to packing and managing Oozie jobs. As an example, each job is likely to share certain properties such as name node and job tracker. Is there an easy way to centralize those properties? Second, we maintain a Nexus repository to store our Java artifacts. Is there an easy way to integrate that with Hadoop/Oozie? Thanks, Shawn Hermans
