[
https://issues.apache.org/jira/browse/OOZIE-1381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13884408#comment-13884408
]
Ryota Egashira commented on OOZIE-1381:
---------------------------------------
thanks. I also checked against 23 and didn't see the issue. since we have been
using 23 at Y!, we didn't catch this regression.
> 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: 4.0.0
>
> 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 was sent by Atlassian JIRA
(v6.1.5#6160)
