hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jothi Padmanabhan (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-6334) GenericOptionsParser does not understand uri for -files -libjars and -archives option
Date Wed, 28 Oct 2009 10:51:59 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-6334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12770892#action_12770892

Jothi Padmanabhan commented on HADOOP-6334:

This is one possible approach. But I am thinking we could follow another approach. 

Have the Path methods (makeQualified, toString) handle fragments as in patch-6334-1.txt, but
do not modify the constructors. 
Modify GOP to construct a URI out of the String as in patch-6334-2.txt and use it to construct
the Path with the Path(URI) constructor. 

Since the Path(URI) constructor directly sets the underlying URI and if the Path methods recognize
fragments, we should be fine and will not have problems of backward compatibility, no? 

> GenericOptionsParser does not understand uri for -files -libjars and -archives option
> -------------------------------------------------------------------------------------
>                 Key: HADOOP-6334
>                 URL: https://issues.apache.org/jira/browse/HADOOP-6334
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: util
>            Reporter: Amareshwari Sriramadasu
>            Assignee: Amareshwari Sriramadasu
>             Fix For: 0.22.0
>         Attachments: patch-6334-1.txt, patch-6334-2.txt, patch-6334.txt
> If we give an uri for -files, -libjars and -archives option , in GenericOptionsParser.
It gives FileNotFoundException.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message