[
https://issues.apache.org/jira/browse/HADOOP-6578?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Todd Lipcon updated HADOOP-6578:
--------------------------------
Description:
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.
was: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.
Summary: Configuration should trim whitespace around a lot of value
types (was: Configuration should trim whitespace around class name values)
> 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
> Priority: Minor
>
> 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.
