-
Notifications
You must be signed in to change notification settings - Fork 8.6k
Support scientific notation for very small numbers #5811
Copy link
Copy link
Closed
Labels
Feature:FieldFormattersFeature:LensFeature:VisualizationsGeneric visualization features (in case no more specific feature label is available)Generic visualization features (in case no more specific feature label is available)Team:VisualizationsTeam label for Lens, elastic-charts, Graph, legacy editors (TSVB, Visualize, Timelion) t//Team label for Lens, elastic-charts, Graph, legacy editors (TSVB, Visualize, Timelion) t//release_note:enhancement
Metadata
Metadata
Assignees
Labels
Feature:FieldFormattersFeature:LensFeature:VisualizationsGeneric visualization features (in case no more specific feature label is available)Generic visualization features (in case no more specific feature label is available)Team:VisualizationsTeam label for Lens, elastic-charts, Graph, legacy editors (TSVB, Visualize, Timelion) t//Team label for Lens, elastic-charts, Graph, legacy editors (TSVB, Visualize, Timelion) t//release_note:enhancement
Type
Fields
Give feedbackNo fields configured for issues without a type.
To overcome the limitation of integer-only intervals on aggs{histogram} queries, I have been using aggs{range} to construct histograms where my fields contain numbers less than one. This works great, but when Kibana 4.3.0 draws the histogram chart, it displays any bin "from:to" values that are less than 0.001 as '0'... see attached pic.

I checked the response body and ElasticSearch v2.1 passes these "from:to" values correctly in scientific format - e.g.
"buckets": {
"0.0-1.0E-4": {
"from": 0,
"from_as_string": "0.0",
"to": 0.0001,
"to_as_string": "1.0E-4",
"doc_count": 104
},
"1.0E-4-2.0E-4": {
"from": 0.0001,
"from_as_string": "1.0E-4",
"to": 0.0002,
"to_as_string": "2.0E-4",
"doc_count": 19
},
...so Kibana is rounding down values it uses on the x-axis.
Would it be possible to preserve the scientific notation, say for numbers less than 0.01?
Full text of request and response follows...
request_body.txt
response_body.txt