Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: common-issues@hadoop.apache.org
Message-ID: <1945441828.225431268395767369.JavaMail.jira@brutus.apache.org>
Date: Fri, 12 Mar 2010 12:09:27 +0000 (UTC)
From: "Michele (@pirroh) Catasta (JIRA)" <jira@apache.org>
To: common-issues@hadoop.apache.org
Subject: [jira] Updated: (HADOOP-6578) Configuration should trim whitespace
 around a lot of value types
In-Reply-To: <420098299.401991266618387947.JavaMail.jira@brutus.apache.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Michele (@pirroh) Catasta updated HADOOP-6578:
----------------------------------------------

    Attachment: HADOOP-6578.patch

Tests were failing because of a missing null check in getTrimmed(). Attached a new patch and re-submitted to Hudson.

> Configuration should trim whitespace around a lot of value types
> ----------------------------------------------------------------
>
>                 Key: HADOOP-6578
>                 URL: https://issues.apache.org/jira/browse/HADOOP-6578
>             Project: Hadoop Common
>          Issue Type: Improvement
>          Components: conf
>    Affects Versions: 0.22.0
>            Reporter: Todd Lipcon
>            Assignee: Michele (@pirroh) Catasta
>            Priority: Minor
>         Attachments: HADOOP-6578.patch
>
>
> I've seen multiple users make an error where they've listed some whitespace around a class name (eg for configuring a scheduler). This results in a ClassNotFoundException which is very hard to debug, as you don't notice the whitespace in the exception! We should simply trim the whitespace in Configuration.getClass and Configuration.getClasses to avoid this class of user error.
> Similarly, we should trim in getInt, getLong, etc - anywhere that whitespace doesn't have semantic meaning we should be a little less strict on input.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.