[
https://issues.apache.org/jira/browse/HADOOP-4864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12773390#action_12773390
]
Amareshwari Sriramadasu commented on HADOOP-4864:
-------------------------------------------------
The same patch applies to Yahoo! distribution branch 0.20 also.
> -libjars with multiple jars broken when client and cluster reside on
> different OSs
> ----------------------------------------------------------------------------------
>
> Key: HADOOP-4864
> URL: https://issues.apache.org/jira/browse/HADOOP-4864
> Project: Hadoop Common
> Issue Type: Bug
> Components: filecache
> Affects Versions: 0.19.0
> Environment: When your hadoop job spans OSs.
> Reporter: Stuart White
> Assignee: Amareshwari Sriramadasu
> Priority: Minor
> Fix For: 0.21.0
>
> Attachments: patch-4864-1.txt, patch-4864.txt, patch.txt
>
> Original Estimate: 1h
> Remaining Estimate: 1h
>
> When submitting a hadoop job from Windows (Cygwin) to a Linux hadoop cluster
> (or vice versa), and when you specify multiple additional jar files via the
> -libjars flag, hadoop throws a ClassNotFoundException for any classes located
> in the additional jars specified via the -libjars flag.
> This is caused by the fact that hadoop uses
> system.getProperty("path.separator") as the delimiter in the list of jar
> files passed via -libjars.
> My suggested solution is to use a comma as the delimiter, rather than the
> path.separator.
> I realize comma is, perhaps, a poor choice for a delimiter because it is
> valid in filenames on both Windows and Linux, but the -libjars flag uses it
> as the delimiter when listing the additional required jars. So, I figured if
> it's already being used as a delimiter, then it's reasonable to use it
> internally as well.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
