Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

json unmarshalling of large numbers #12

Closed
rompic opened this issue Nov 19, 2016 · 2 comments
Closed

json unmarshalling of large numbers #12

rompic opened this issue Nov 19, 2016 · 2 comments

Comments

@rompic
Copy link
Contributor

rompic commented Nov 19, 2016

endpoint provides:
"values":[265381,276756,16476547,42900243,44762036, ...

httpbeat pushes:

"values": [
265381,
276756,
1.6476547e+07,
4.2900243e+07,
4.4762036e+07,

this leads to an error when using graylog as logstash destination:
[12]: index [graylog2_17], type [message], id [e6449a00-ae49-11e6-bf3c-5e4abd8a540e], message [MapperParsingException[failed to parse]; nested: IllegalArgumentException[mapper [beat_response_jsonBody_snapshot_values] of different type, current_type [long], merged_type [double]];]

potential solution in:
http://stackoverflow.com/questions/22343083/json-marshaling-with-long-numbers-in-golang-gives-floating-point-number
@rompic rompic changed the title json nmarshalling of large numbers json unmarshalling of large numbers Nov 19, 2016
christiangalsterer added a commit that referenced this issue Dec 18, 2016
@christiangalsterer
Feature:
395bbdf 
* [Output format of response body is now defined via output_format parameter](#8). Default is 'string'

Bugfixes
* [Missing es2x template](#13)
* [Correct parsing of large numbers in JSON output](#12)
@christiangalsterer
Copy link
Owner

Fix and released with version 3.0.0

@rompic
Copy link
Contributor Author

rompic commented Dec 18, 2016

thx!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@christiangalsterer @rompic