-
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
[Input Controls] Make dynamic options limit size configurable #47453
Comments
Pinging @elastic/kibana-app (Team:KibanaApp) |
Hi @alvarellos for more options to show up you have to start typing, then the options will be filtered down. If the values you are looking for are still now showing up, you might run into the default timeout of fetching the terms. Is there a little warning triangle next to the label? If yes then you might have to adjust your |
Hi,
My question would be.. Thanks |
If you're using "dynamic options" it will mean the search box will filter down while you're filtering (especially designed for larger datasets). We will always only load 10 entries for your search, since that would otherwise potentially very easily take way too much time on larger clusters. If you continue typing you'll filter further down into your data and a new search will be executed that will retrieve you the more filtered down results. This setting is also not configurable currently. I am rewriting this PR as an enhancement request to change the amount of results loaded for each search when typing. |
Another example of this limitation: https://discuss.elastic.co/t/controls-still-not-showing-all-possibilities/220616/3 |
Closing this one in favour of this one #140174 |
Kibana version:
v7.4.0
Describe the feature:
Controls Visualization (Experimental)
Steps done:
Controls > Options list > add
Add the index patern, Field and Parent control
Multiselect selected
Dynamic options selected
Problem: not all the options are shown in the dropdown fields created.
Is there a limitation on how many options can be shown ?
The text was updated successfully, but these errors were encountered: