hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-3453) HDFS does not use ClientProtocol in a backward-compatible way
Date Tue, 29 May 2012 14:15:23 GMT

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

Hadoop QA commented on HDFS-3453:
---------------------------------

-1 overall.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12530042/hdfs-3453-branch-1.patch
  against trunk revision .

    +1 @author.  The patch does not contain any @author tags.

    -1 tests included.  The patch doesn't appear to include any new or modified tests.
                        Please justify why no new tests are needed for this patch.
                        Also please list what manual steps were performed to verify this patch.

    -1 patch.  The patch command could not apply the patch.

Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/2531//console

This message is automatically generated.
                
> HDFS does not use ClientProtocol in a backward-compatible way
> -------------------------------------------------------------
>
>                 Key: HDFS-3453
>                 URL: https://issues.apache.org/jira/browse/HDFS-3453
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: hdfs client
>    Affects Versions: 1.0.0
>            Reporter: Kihwal Lee
>            Assignee: Kihwal Lee
>             Fix For: 1.1.0
>
>         Attachments: hdfs-3453-branch-1.patch, hdfs-3453-branch-1.patch
>
>
> HDFS-617 was brought into branch-0.20-security/branch-1 to support non-recursive create,
along with HADOOP-6840 and HADOOP-6886. However, the changes in HDFS was done in an incompatible
way, making the client unusable against older clusters, even when plain old create() is called.
This is because DFS now internally calls create() through the newly introduced method. By
simply changing how the methods are wired internally, we can remove this limitation. We may
eventually switch back to the approach in HDFS-617 when the majority of users adopt branch-1
based releases.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message