Return-Path: X-Original-To: apmail-hadoop-hdfs-issues-archive@minotaur.apache.org Delivered-To: apmail-hadoop-hdfs-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 819FBCC56 for ; Tue, 22 May 2012 19:31:42 +0000 (UTC) Received: (qmail 92290 invoked by uid 500); 22 May 2012 19:31:42 -0000 Delivered-To: apmail-hadoop-hdfs-issues-archive@hadoop.apache.org Received: (qmail 92179 invoked by uid 500); 22 May 2012 19:31:42 -0000 Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: hdfs-issues@hadoop.apache.org Delivered-To: mailing list hdfs-issues@hadoop.apache.org Received: (qmail 92088 invoked by uid 99); 22 May 2012 19:31:41 -0000 Received: from issues-vm.apache.org (HELO issues-vm) (140.211.11.160) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 22 May 2012 19:31:41 +0000 Received: from isssues-vm.apache.org (localhost [127.0.0.1]) by issues-vm (Postfix) with ESMTP id E45D414280B for ; Tue, 22 May 2012 19:31:41 +0000 (UTC) Date: Tue, 22 May 2012 19:31:41 +0000 (UTC) From: "Kihwal Lee (JIRA)" To: hdfs-issues@hadoop.apache.org Message-ID: <395808871.9280.1337715101938.JavaMail.jiratomcat@issues-vm> In-Reply-To: <1505249907.7816.1337693861384.JavaMail.jiratomcat@issues-vm> Subject: [jira] [Commented] (HDFS-3453) HDFS does not use ClientProtocol in a backward-compatible way MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HDFS-3453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13281167#comment-13281167 ] Kihwal Lee commented on HDFS-3453: ---------------------------------- Manually ran test-patch {noformat} [exec] -1 overall. [exec] [exec] +1 @author. The patch does not contain any @author tags. [exec] [exec] -1 tests included. The patch doesn't appear to include any new or modified tests. [exec] Please justify why no tests are needed for this patch. [exec] [exec] +1 javadoc. The javadoc tool did not generate any warning messages. [exec] [exec] +1 javac. The applied patch does not increase the total number of javac compiler warnings. [exec] [exec] -1 findbugs. The patch appears to introduce 8 new Findbugs (version 1.3.9) warnings. {noformat} * test : No test was added since there is no functional change within the build/release. * findbugs : Contrary to the report, this change does not introduce any additional findbug warnings. > 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-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