[
https://issues.apache.org/jira/browse/OOZIE-1685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13992889#comment-13992889
]
Hadoop QA commented on OOZIE-1685:
----------------------------------
Testing JIRA OOZIE-1685
Cleaning local git workspace
----------------------------
{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:red}-1 RAW_PATCH_ANALYSIS{color}
. {color:green}+1{color} the patch does not introduce any @author tags
. {color:green}+1{color} the patch does not introduce any tabs
. {color:red}-1{color} the patch contains 2 line(s) with trailing spaces
. {color:red}-1{color} the patch contains 1 line(s) longer than 132
characters
. {color:green}+1{color} the patch does adds/modifies 4 testcase(s)
{color:green}+1 RAT{color}
. {color:green}+1{color} the patch does not seem to introduce new RAT
warnings
{color:green}+1 JAVADOC{color}
. {color:green}+1{color} the patch does not seem to introduce new Javadoc
warnings
{color:green}+1 COMPILE{color}
. {color:green}+1{color} HEAD compiles
. {color:green}+1{color} patch compiles
. {color:green}+1{color} the patch does not seem to introduce new javac
warnings
{color:green}+1 BACKWARDS_COMPATIBILITY{color}
. {color:green}+1{color} the patch does not change any JPA
Entity/Colum/Basic/Lob/Transient annotations
. {color:green}+1{color} the patch does not modify JPA files
{color:red}-1 TESTS{color} - patch does not compile, cannot run testcases
{color:green}+1 DISTRO{color}
. {color:green}+1{color} distro tarball builds with the patch
----------------------------
{color:red}*-1 Overall result, please check the reported -1(s)*{color}
The full output of the test-patch run is available at
. https://builds.apache.org/job/oozie-trunk-precommit-build/1222/
> Oozie doesn’t process correctly workflows with a non-default name node
> ----------------------------------------------------------------------
>
> Key: OOZIE-1685
> URL: https://issues.apache.org/jira/browse/OOZIE-1685
> Project: Oozie
> Issue Type: Bug
> Components: core
> Affects Versions: trunk, 3.3.2, 4.0.0
> Environment: Any
> Reporter: Benjamin Zhitomirsky
> Fix For: trunk
>
> Attachments: Design of the fix OOZIE-1685-rev1.docx,
> oozie-1685-trunk.patch, oozie-1685-trunk.patch, oozie-1685-trunk.patch,
> oozie-1685.1.patch, oozie-1685.2.patch, oozie-1685.3.patch, oozie-1685.4.patch
>
> Original Estimate: 168h
> Remaining Estimate: 168h
>
> 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.
> I will submit a fix for CR soon. Please refer attached short document for
> more information.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
