[
https://issues.apache.org/jira/browse/OOZIE-2400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15136939#comment-15136939
]
Hadoop QA commented on OOZIE-2400:
----------------------------------
Testing JIRA OOZIE-2400
Cleaning local git workspace
----------------------------
{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:green}+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:green}+1{color} the patch does not introduce any trailing spaces
. {color:green}+1{color} the patch does not introduce any line longer than
132
. {color:green}+1{color} the patch does adds/modifies 2 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}
. Tests run: 1762
. Tests failed: 10
. Tests errors: 2
. The patch failed the following testcases:
. testRun(org.apache.oozie.client.TestOozieCLI)
. testSubmitDoAs(org.apache.oozie.client.TestOozieCLI)
. testSubmitWithPropertyArguments(org.apache.oozie.client.TestOozieCLI)
. testSubmit(org.apache.oozie.client.TestOozieCLI)
. testReRun(org.apache.oozie.client.TestOozieCLI)
. testRunWithDebug(org.apache.oozie.client.TestOozieCLI)
. testJobDryrun(org.apache.oozie.client.TestOozieCLI)
. testForNoDuplicates(org.apache.oozie.event.TestEventGeneration)
. testSamplers(org.apache.oozie.util.TestMetricsInstrumentation)
.
testCoordStatus_Failed(org.apache.oozie.command.coord.TestCoordChangeXCommand)
{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/2734/
> Workflow xml configuration parser cannot deal with namespace prefix
> -------------------------------------------------------------------
>
> Key: OOZIE-2400
> URL: https://issues.apache.org/jira/browse/OOZIE-2400
> Project: Oozie
> Issue Type: Bug
> Components: core
> Affects Versions: trunk, 4.1.0, 4.2.0, 4.3.0
> Environment: Oracle Linux 6.6, Oozie 4.1.0, Cloudera CDH 5.4.2
> Reporter: Roman Krüger
> Assignee: Lars Francke
> Labels: easyfix
> Fix For: trunk, 4.1.0, 4.2.0, 4.3.0
>
> Attachments: OOZIE-2400-1.patch, OOZIE-2400.2.patch
>
> Original Estimate: 2h
> Remaining Estimate: 2h
>
> When running a java action and a spark action via an oozie workflow xml, the
> xml contains multiple namespaces (e.g. uri:oozie:workflow:0.5 and
> uri:oozie:spark-action:0.1).
> Thus the elements need to be prefixed by the namespace prefix. But when
> running this workflow, the configuration parser throws the exception "*JA009:
> bad conf file: top-level element not <configuration>*".
> The bug is located in class org.apache.oozie.util.XConfiguration in methods
> "parseDocument(Document doc)" and "processNodes(Element root)". The xml tags
> here are retrieved via "getTagName()", (which gets the full tag name) and
> compared against string constants like "configuration". So this fails in case
> the tag contains a namespace prefix and it seems there is no workaround!
> Here is an easy fix for this. All calls of "getTagName()" in these 2 methods
> can be replaced by "getLocalName()".
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
