hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eli Collins (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HADOOP-2081) Configuration getInt, getLong, and getFloat replace invalid numbers with the default value
Date Mon, 18 Jul 2011 17:02:57 GMT

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

Eli Collins updated HADOOP-2081:
--------------------------------

    Release Note: Invalid configuration values now result in a number format exception rather
than the default value being used.
    Hadoop Flags: [Incompatible change, Reviewed]  (was: [Incompatible change])

+1  latest patch looks good.

> Configuration getInt, getLong, and getFloat replace invalid numbers with the default
value
> ------------------------------------------------------------------------------------------
>
>                 Key: HADOOP-2081
>                 URL: https://issues.apache.org/jira/browse/HADOOP-2081
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: conf
>    Affects Versions: 0.22.0
>            Reporter: Owen O'Malley
>            Assignee: Harsh J
>             Fix For: 0.23.0
>
>         Attachments: HADOOP-2081.r1.diff, HADOOP-2081.r2.diff, HADOOP-2081.r3.diff
>
>
> The current behavior of silently replace invalid numbers in the configuration with the
default value leads to hard to diagnose problems. The methods should throw an exception to
signal that the input was invalid.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message