[ 
https://issues.apache.org/jira/browse/OOZIE-1381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13675546#comment-13675546
 ] 

Hadoop QA commented on OOZIE-1381:
----------------------------------

Testing JIRA OOZIE-1381

Cleaning local svn 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:red}WARNING{color}: the current HEAD has 1 Javadoc warning(s)
{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: 1248
.    Tests failed: 2
.    Tests errors: 3

.    The patch failed the following testcases:

.      testForNoDuplicates(org.apache.oozie.event.TestEventGeneration)
.      testWorkflowJobEvent(org.apache.oozie.event.TestEventGeneration)

{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}

{color:red}.   There is at least one warning, please check{color}

The full output of the test-patch run is available at

.   https://builds.apache.org/job/oozie-trunk-precommit-build/558/
                
> Oozie does not support access to the distributed cache file under different 
> name node 
> --------------------------------------------------------------------------------------
>
>                 Key: OOZIE-1381
>                 URL: https://issues.apache.org/jira/browse/OOZIE-1381
>             Project: Oozie
>          Issue Type: Bug
>    Affects Versions: trunk
>            Reporter: Ryota Egashira
>            Assignee: Ryota Egashira
>             Fix For: trunk
>
>         Attachments: OOZIE-1381-v2.patch, OOZIE-1381-v5.patch
>
>
> suppose app path on name node NN1, and user wants to dist-cache file located 
> on different name node, NN2. when user specify something like 
> "<file>hdfs://nn2_address:8020/target_file</file>", it doesn't work due to 
> current JavaActionExecutor.addToCache logic, which extracts file path and 
> prepends NN1.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to