DEV: Quotation marks removed for numeric values #100
Conversation
|
Traffic Server counters are int64 ... can ElasticSearch deal with that, or is it constrained to JavaScript compatible numeric types? |
|
It follows Java convention. See link. However you can configure each item with explicit mapping when required. |
| @@ -1 +0,0 @@ | |||
| Subproject commit 880ca300e8fb7b432b9d25ed377db2102e4cb63d | |||
There was a problem hiding this comment.
this should probably not be part of the commit
There was a problem hiding this comment.
Yes, it is by mistake. You can ignore this line.
|
OK, this needs to be a plugin option then. Some consumers will expect javascript types and others will prefer richer integral types. The best thing to do here might be to serve 2 endpoints with the different semantics. |
|
I have a patch that adds 2 new options to enable emitting JSON numbers, and to enable wrapping JSON numbers to int64. |
Doc: Update po files in reference/configuration/
Remove unnecessary volatile
This reverts commit 2082219.
In "Stats over Http" plugin, it is better if integer and floating values does not have quotation marks in JSON output. With this change, JSON output works with data loggers based on elasticsearch with minimal configuration.