-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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.
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
precision_threshold error for certain aggregation types #7804
Comments
Hi @doingitbigdata. As you guessed, |
`v95.1.0`⏩`v95.2.0` _[Questions? Please see our Kibana upgrade FAQ.](https://github.com/elastic/eui/blob/main/wiki/eui-team-processes/upgrading-kibana.md#faq-for-kibana-teams)_ --- ## [`v95.2.0`](https://github.com/elastic/eui/releases/v95.2.0) - Updated `EuiContextMenuItemIcon`'s type definition to explicitly define support for `EuiIcon`'s `IconType` ([#7804](elastic/eui#7804)) - Updated `EuiSteps` to support a new `titleSize="xxs"` style, which outputs the same title font size but smaller unnumbered step indicators ([#7813](elastic/eui#7813)) - Updated `EuiStepsHorizontal` to support a new `size="xs"` style, which outputs smaller unnumbered step indicators ([#7813](elastic/eui#7813)) - Updated `EuiStepNumber` to support new `titleSize="none"` which omits rendering step numbers, and will only render icons ([#7813](elastic/eui#7813)) - Updated `setEuiDevProviderWarning` to additionally accept a custom callback function, which warning messages will be passed to ([#7820](elastic/eui#7820)) - Updated `EuiIcon` to feature updated `logoElasticStack` logo for referencing Elastic Stack platform ([#7838](elastic/eui#7838)) - Updated `EuiIcon` to feature updated `casesApp` design. ([#7840](elastic/eui#7840)) - Updated `EuiComboBox` to no longer autocomplete searched text when used within forms ([#7842](elastic/eui#7842)) **CSS-in-JS conversions** - Converted `EuiFilePicker` to Emotion; Removed `$euiFilePickerTallHeight` ([#7833](elastic/eui#7833)) --------- Co-authored-by: Jon <[email protected]>
Kibana version: 4.5.3
Browser version: Google Chrome Version 51.0.2704.103 m
Description of the problem including expected versus actual behavior:
Error when using precision_threshold for certain aggregation types (e.g. Average, Sum, Max).
I'm not sure if "precision_threshold" is supported for these aggregation types by elasticsearch. I would like to use it as I am finding the values returned to be inaccurate.
Steps to reproduce:
Errors in browser console (if relevant):
Provide logs and/or server output (if relevant):
Error: Request to Elasticsearch failed: {"error":{"root_cause":[{"type":"search_parse_exception","reason":"Unexpected token VALUE_NUMBER in [1].","line":1,"col":295}],"type":"search_phase_execution_exception","reason":"all shards failed","phase":"query","grouped":true,"failed_shards":[{"shard":0,"index":"pcrf-oplog-2016.24","node":"JgvUiZWrTtChEWpYflKZuA","reason":{"type":"search_parse_exception","reason":"Unexpected token VALUE_NUMBER in [1].","line":1,"col":295}}]}}
at http://kll0161:5601/bundles/kibana.bundle.js?v=9910:80333:39
at Function.Promise.try (http://kll0161:5601/bundles/commons.bundle.js?v=9910:61139:23)
at http://kll0161:5601/bundles/commons.bundle.js?v=9910:61108:31
at Array.map (native)
at Function.Promise.map (http://kll0161:5601/bundles/commons.bundle.js?v=9910:61107:31)
at callResponseHandlers (http://kll0161:5601/bundles/kibana.bundle.js?v=9910:80305:23)
at http://kll0161:5601/bundles/kibana.bundle.js?v=9910:79810:17
at processQueue (http://kll0161:5601/bundles/commons.bundle.js?v=9910:42385:29)
at http://kll0161:5601/bundles/commons.bundle.js?v=9910:42401:28
at Scope.$eval (http://kll0161:5601/bundles/commons.bundle.js?v=9910:43629:29)
The text was updated successfully, but these errors were encountered: