----------------------------------------------------------- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/19929/ -----------------------------------------------------------
Review request for oozie. Repository: oozie-git Description ------- When <name-node> element in Oozie workflow specifies a name node different from the default one (specified in core-site.xml), the following functionality doesn’t work properly: ?Location of libraries specified via oozie.service.WorkflowAppService.system.libpath. Oozie first (during launcher configuration) tries to locate them using name node specified by the <name-node> element, but later during job submission it expects this path to be under the default Oozie name node ?Processing of the job-xml element if job xml is specified via absolute path. Oozie tries locate it under the default Oozie name node instead of the name-node specified in action. Specifying non-default name node makes a lot of sense in Azure environment, because it allows to submit the same job to different Hadoop clusters. Diffs ----- core/src/main/java/org/apache/oozie/action/hadoop/JavaActionExecutor.java 68d77a8 core/src/test/java/org/apache/oozie/action/hadoop/ActionExecutorTestCase.java bc2c1b6 core/src/test/java/org/apache/oozie/action/hadoop/TestJavaActionExecutor.java 7841076 core/src/test/java/org/apache/oozie/test/XFsTestCase.java 18cb742 core/src/test/java/org/apache/oozie/test/XTestCase.java 1536927 Diff: https://reviews.apache.org/r/19929/diff/ Testing ------- On deployed Hadoop cluster. Two tests were added. Thanks, Benjamin Zhitomirsky
