Return-Path: X-Original-To: apmail-hadoop-common-issues-archive@minotaur.apache.org Delivered-To: apmail-hadoop-common-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 4BF6E7A4F for ; Sat, 5 Nov 2011 15:25:13 +0000 (UTC) Received: (qmail 42748 invoked by uid 500); 5 Nov 2011 15:25:13 -0000 Delivered-To: apmail-hadoop-common-issues-archive@hadoop.apache.org Received: (qmail 42650 invoked by uid 500); 5 Nov 2011 15:25:13 -0000 Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: common-issues@hadoop.apache.org Delivered-To: mailing list common-issues@hadoop.apache.org Received: (qmail 42642 invoked by uid 99); 5 Nov 2011 15:25:13 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 05 Nov 2011 15:25:13 +0000 X-ASF-Spam-Status: No, hits=-2001.2 required=5.0 tests=ALL_TRUSTED,RP_MATCHES_RCVD X-Spam-Check-By: apache.org Received: from [140.211.11.116] (HELO hel.zones.apache.org) (140.211.11.116) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 05 Nov 2011 15:25:11 +0000 Received: from hel.zones.apache.org (hel.zones.apache.org [140.211.11.116]) by hel.zones.apache.org (Postfix) with ESMTP id 9DC36364D1 for ; Sat, 5 Nov 2011 15:24:51 +0000 (UTC) Date: Sat, 5 Nov 2011 15:24:51 +0000 (UTC) From: "Hadoop QA (Commented) (JIRA)" To: common-issues@hadoop.apache.org Message-ID: <668585643.3062.1320506691647.JavaMail.tomcat@hel.zones.apache.org> In-Reply-To: <705417386.25313.1319733752748.JavaMail.tomcat@hel.zones.apache.org> Subject: [jira] [Commented] (HADOOP-7777) Implement a base class for DNSToSwitchMapping implementations that can offer extra topology information 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/HADOOP-7777?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13144720#comment-13144720 ] Hadoop QA commented on HADOOP-7777: ----------------------------------- -1 overall. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12502596/HADOOP-7777-switch.patch against trunk revision . +1 @author. The patch does not contain any @author tags. +1 tests included. The patch appears to include 10 new or modified tests. +1 javadoc. The javadoc tool did not generate any warning messages. -1 javac. The applied patch generated 1040 javac compiler warnings (more than the trunk's current 1039 warnings). -1 findbugs. The patch appears to introduce 7 new Findbugs (version 1.3.9) warnings. +1 release audit. The applied patch does not increase the total number of release audit warnings. +1 core tests. The patch passed unit tests in . +1 contrib tests. The patch passed contrib unit tests. Test results: https://builds.apache.org/job/PreCommit-HADOOP-Build/360//testReport/ Findbugs warnings: https://builds.apache.org/job/PreCommit-HADOOP-Build/360//artifact/trunk/hadoop-common-project/patchprocess/newPatchFindbugsWarningshadoop-common.html Console output: https://builds.apache.org/job/PreCommit-HADOOP-Build/360//console This message is automatically generated. > Implement a base class for DNSToSwitchMapping implementations that can offer extra topology information > ------------------------------------------------------------------------------------------------------- > > Key: HADOOP-7777 > URL: https://issues.apache.org/jira/browse/HADOOP-7777 > Project: Hadoop Common > Issue Type: Improvement > Components: util > Affects Versions: 0.23.0, 0.24.0 > Reporter: Steve Loughran > Assignee: Steve Loughran > Attachments: HADOOP-7777-switch.patch, HADOOP-7777-switch.patch, HADOOP-7777-switch.patch > > > HDFS-2492 has identified a need for DNSToSwitchMapping implementations to provide a bit more topology information (e.g. whether or not there are multiple switches). This could be done by writing an extended interface, querying its methods if present and coming up with a default action if there is no extended interface. > Alternatively, we have a base class that all the standard mappings implement, with a boolean isMultiRack() method; all the standard subclasses would extend this, as could any third party topology provider. The advantage of this approach is that it is easier to add new operations without going into a multi-interface mess. -- 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