Closed vldbnc closed 1 year ago
Hey, it's doing a terms aggregation with a limit - fetching all results at the elasticsearch level could cause slow queries and hangups on larger data sets. Does a more specific search work? Maybe a configurable limit could help.
Pinging @elastic/kibana-app
There are also the kibana.autocompleteTimeout
and kibana.autocompleteTerminateAfter
that might help in this case: https://www.elastic.co/guide/en/kibana/current/settings.html
@flash1293 @jbudz index is small-sized consisting of 59k records but I will check those settings. Thanks
I believe that a custom limit is a must feature. Optionally, I'd appreciate a custom sort. Thanks.
I've got the same problem, but in my case auto-completion is not required since users are expected to just copy past a value.
Is that possible to configure the control to just be a shortcut to add a filter ? Without having it trying to fetch any data nor trying to provide a list in which users are supposed to choose ?
The search of the new input controls should no longer have this issue + the new options list control now has a dropdown that allows the values to be sorted by document count and/or alphabetically . :+1:
Kibana version: 7.3.0 Elasticsearch version: 7.3.0 Server OS version: Linux qdeqnm 4.15.0-54-generic #58-Ubuntu SMP Mon Jun 24 10:55:24 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux Browser version: Chrome Browser OS version: Version 75.0.3770.142 (Official Build) (64-bit) Original install method (e.g. download page, yum, from source, etc.): docker pull kibana:7.3.0
Describe the bug: Property is index as keyword datavalue but input controls does not list all options. The same issue is seen also for integer long-values.
Expected behavior:
Screenshots (if relevant):
Errors in browser console (if relevant):
Provide logs and/or server output (if relevant):
Any additional context: