You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@storm.apache.org by "Rick Kellogg (JIRA)" <ji...@apache.org> on 2015/10/05 04:13:26 UTC

[jira] [Updated] (STORM-328) Config.java and Utils.get{Int,Long} are not in sync for floating point

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

Rick Kellogg updated STORM-328:
-------------------------------
    Component/s: storm-core

> Config.java and Utils.get{Int,Long} are not in sync for floating point
> ----------------------------------------------------------------------
>
>                 Key: STORM-328
>                 URL: https://issues.apache.org/jira/browse/STORM-328
>             Project: Apache Storm
>          Issue Type: Bug
>          Components: storm-core
>    Affects Versions: 0.9.2-incubating, 0.9.1-incubating, 0.9.0.1
>            Reporter: Robert Joseph Evans
>            Assignee: Jungtaek Lim
>              Labels: newbie
>             Fix For: 0.9.3
>
>
> For most numeric configuration values Config.java has a type of Number listed, but the values are parsed using Utils.getInt or Utils.getLong, which means if someone gave a floating point number it would pass the ConfigValidation, but would blow up when it is used.  This is most critical for values that Nimbus reads, but would be good to have them consistent everywhere.
> We should also check that getInt works properly for numbers that are larger then would fit in an integer.
> Either we need to update Utils to be more lenient when looking at doubles, or we need to make Config more strict, which may be difficult with the YAML and JSON parsing that happens, where ints are often converted into longs.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)