You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@oozie.apache.org by "Ryota Egashira (JIRA)" <ji...@apache.org> on 2013/05/17 21:41:16 UTC

[jira] [Commented] (OOZIE-1381) Oozie does not support access to the distributed cache file under different name node

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

Ryota Egashira commented on OOZIE-1381:
---------------------------------------

still WIP in terms of test,
https://reviews.apache.org/r/11228
                
> 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
>            Reporter: Ryota Egashira
>            Assignee: Ryota Egashira
>
> 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