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

Hudson commented on HADOOP-8310:
--------------------------------

Integrated in Hadoop-Hdfs-0.23-Build #392 (See 
[https://builds.apache.org/job/Hadoop-Hdfs-0.23-Build/392/])
    svn merge -c 1331007 FIXES: HADOOP-8310. FileContext#checkPath should 
handle URIs with no port. Contributed by Aaron T. Myers. (Revision 1392622)

     Result = UNSTABLE
jlowe : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1392622
Files : 
* 
/hadoop/common/branches/branch-0.23/hadoop-common-project/hadoop-common/CHANGES.txt
* 
/hadoop/common/branches/branch-0.23/hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/fs/AbstractFileSystem.java
* 
/hadoop/common/branches/branch-0.23/hadoop-common-project/hadoop-common/src/test/java/org/apache/hadoop/fs/TestAfsCheckPath.java

                
> FileContext#checkPath should handle URIs with no port
> -----------------------------------------------------
>
>                 Key: HADOOP-8310
>                 URL: https://issues.apache.org/jira/browse/HADOOP-8310
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: fs
>    Affects Versions: 2.0.0-alpha
>            Reporter: Aaron T. Myers
>            Assignee: Aaron T. Myers
>             Fix For: 2.0.0-alpha, 0.23.4
>
>         Attachments: HADOOP-8310.patch
>
>
> AbstractFileSystem#checkPath is used to verify that a given path is for the 
> same file system as represented by the AbstractFileSystem instance.
> The original intent of the code was to allow for no port to be provided in 
> the checked path, if the default port was being used by the 
> AbstractFileSystem instance. However, before performing port handling, 
> AFS#checkPath compares the full URI authorities for equality. Since the URI 
> authority includes the port, the port handling code is never reached, and 
> thus valid paths may be erroneously considered invalid.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to