Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: common-issues@hadoop.apache.org
Date: Fri, 16 Mar 2012 05:47:45 +0000 (UTC)
From: "Colin Patrick McCabe (Updated) (JIRA)" <jira@apache.org>
To: common-issues@hadoop.apache.org
Message-ID: 
 <488854031.23082.1331876865081.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <933274554.46681.1331341619507.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Updated] (HADOOP-8159) NetworkTopology: getLeaf should
 check for invalid topologies
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/HADOOP-8159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Colin Patrick McCabe updated HADOOP-8159:
-----------------------------------------

    Attachment: HADOOP-8159.006.patch

address eli's comments
                
> NetworkTopology: getLeaf should check for invalid topologies
> ------------------------------------------------------------
>
>                 Key: HADOOP-8159
>                 URL: https://issues.apache.org/jira/browse/HADOOP-8159
>             Project: Hadoop Common
>          Issue Type: Bug
>    Affects Versions: 1.0.0
>            Reporter: Colin Patrick McCabe
>            Assignee: Colin Patrick McCabe
>             Fix For: 1.0.0
>
>         Attachments: HADOOP-8159-b1.005.patch, HADOOP-8159.005.patch, HADOOP-8159.006.patch
>
>
> Currently, in NetworkTopology, getLeaf doesn't do too much validation on the InnerNode object itself. This results in us getting ClassCastException sometimes when the network topology is invalid. We should have a less confusing exception message for this case.

--
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