[
https://issues.apache.org/jira/browse/HADOOP-2081?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13590374#comment-13590374
]
Harsh J commented on HADOOP-2081:
---------------------------------
Hi Shobin,
I believe you should file a new bug against Vaidya. If it expects to read a
float (mostly percentages) value as int, it is doing things wrong and will
almost always read them as 0, and do its computation inaccurately. Please do
file a new MR JIRA against Vaidya component, preferably with a patch that
changes its getInt call to someting more appropriate/correct.
This change is not the real bug you're facing, its just bought it to the front.
> 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.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
