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 2014/02/01 09:22:10 UTC

[jira] [Commented] (OOZIE-1675) Adding absolute URI of local cluster to dist cache not working with hadoop-1

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

Ryota Egashira commented on OOZIE-1675:
---------------------------------------

+1

> Adding absolute URI of local cluster to dist cache not working with hadoop-1
> ----------------------------------------------------------------------------
>
>                 Key: OOZIE-1675
>                 URL: https://issues.apache.org/jira/browse/OOZIE-1675
>             Project: Oozie
>          Issue Type: Bug
>    Affects Versions: 4.0.0
>            Reporter: Satish Mittal
>            Assignee: Satish Mittal
>         Attachments: OOZIE-1675.1.patch.txt, OOZIE-1675.2.patch.txt, OOZIE-1675.3.patch.txt
>
>
> On hadoop-1, when oozie adds a file path which is an absoute URI on local cluster (i.e. of form hdfs://NN1-host:port/file-path) to distributed cache, it is not working.
> The issue is 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 true in case of an absolute URI. Till oozie 3.3, absolute paths on local cluster were working because of earlier logic.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)