[
https://issues.apache.org/jira/browse/OOZIE-2512?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15311603#comment-15311603
]
Hadoop QA commented on OOZIE-2512:
----------------------------------
Testing JIRA OOZIE-2512
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 1 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: 1782
. Tests failed: 0
. Tests errors: 1
. The patch failed the following 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/2927/
> ShareLibservice returns incorrect path for jar
> ----------------------------------------------
>
> Key: OOZIE-2512
> URL: https://issues.apache.org/jira/browse/OOZIE-2512
> Project: Oozie
> Issue Type: Bug
> Reporter: Satish Subhashrao Saley
> Assignee: Satish Subhashrao Saley
> Fix For: trunk
>
> Attachments: OOZIE-2512-1.patch, OOZIE-2512-2.patch,
> OOZIE-2512-3.patch, OOZIE-2512-amend-1.patch, OOZIE-2512-amend-2.patch,
> OOZIE-2512-amend-3.patch
>
>
> If we have {{oozie.service.ShareLibService.mapping.file}} setting pointing to
> a metafile, then ShareLibServe loads paths from that file.
> We can mention path to a directory or path to a direct file.
> When path to a directory is mentioned, the paths are populated correctly, but
> not when we mentioned direct path for a file.
> Consider following paths:
> * /sharelib/pig/
> ** pig.jar
> ** some.jar
> * /sharelib/spark
> ** spark-assembly.jar
> In metafile, we have
> {code}
> oozie.pig=/sharelib/pig/
> oozie.spark=/sharelib/spark/spark-assembly.jar
> {code}
> Now, the SharelibService calculates the paths as
> pig -
> hdfs://clustername.com:8020/sharelib/pig/pig.jar,hdfs://clustername.com:8020/sharelib/pig/some.jar
> spark - /sharelib/spark/spark-assembly.jar
> The spark path does not have hdfs prefixed.
> Later on, when we run a spark action, it fails with
> {code}
> Failing Oozie Launcher, Main class
> [org.apache.oozie.action.hadoop.SparkMain], main() threw exception, File
> file:/sharelib/spark/spark-assembly.jar does not exist
> java.io.FileNotFoundException: File file:/sharelib/spark/spark-assembly.jar
> does not exist
> {code}
> Remember, if we already mentioned hdfs prefixed paths in metafile, then it
> works fine.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
