[
https://issues.apache.org/jira/browse/OOZIE-1381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13877420#comment-13877420
]
Satish Mittal commented on OOZIE-1381:
--------------------------------------
Hi,
Has this feature been tested with Hadoop-1 when the file to be added to dist
cache has an absolute URI? We are seeing a regression with oozie 4 on hadoop-1
when file path is an absoute URI on same cluster (i.e. of form
hdfs://NN1-host:port/file-path). It used to work till oozie 3.3.
The issue that tasks spawned by oozie jobs are not getting these paths added to
their classpath and hence failing. In hadoop-1,
DistributedCache.addFileToClasspath() appends paths in classpath with
path.separator (which is ':' on linux). That won't work if ':' character is
present in the path itself, which is the case in absolute URI. Till oozie 3.3,
absolute paths on local cluster were working because of earlier logic.
Thanks,
Satish
> 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)
