convert_datatype changes number value to INTEGER.MAX when its too large

[ppf2]

convert_datatype takes either int or float options today.

However, if you run a long value through the convert_datatype, it allows it. However, the dissect -> convert_datatype will change the value of the field to INTEGER.MAX

Source value:

  "supportID" => "4394740425750718628"

Output value:

"supportID" => 2147483647

To workaround this, instead of using convert_datatype for dissect, I am post-processing it using mutate/convert:

  mutate {
    convert => { "supportID" => "integer" }
  }

Which returns the correct result:

"supportID" => 4394740425750718628

If we do not intend to support longs like mutate/convert does, it will be better if we throw an error on the configuration instead of auto-converting the value to integer.max.

[guyboertje]

You are correct. Will fix. This was me confusing the Ruby Integer (Fixnum) which is actually a Java long.

[guyboertje]

Will be fixed in #34

[guyboertje]

fixed with #34