Dynamic controls cannot be used for unlimited/numeric searches

[slhck]

Kibana version: 7.6.1

Elasticsearch version: 7.6.1

Server OS version: Ubuntu 18.04

Browser version: Firefox

Browser OS version:

Original install method (e.g. download page, yum, from source, etc.): Docker

Describe the bug: I want to use a control to allow the user to select one particular document via ID. A control to search for a numeric ID does not find all IDs. Upon entering a correct ID, it says the ID "does not match any options".

Steps to reproduce:

1. Add a new control visualization
2. Select the index pattern and the field "id"
3. Type in an existing ID into the search field

Expected behavior: The ID should be findable.

Screenshots (if relevant):

This is the control itself:

This is when it does not find the ID 35:

However, the ID exists in the data (and of course, in the corresponding index):

The field is a numeric field, and the index mapping has been refreshed.

I found out that this is because the size of the options (10 in my case) determines the amount of IDs that can be found at all. It was not clear to me, at all, that these options fields are pre-populated and can only be used for a limited set of values in the case of numeric values.

[elasticmachine]

Pinging @elastic/kibana-app (Team:KibanaApp)

[slhck]

I realize now that this really is a bug report turned into a feature request, but for me it manifested as a bug, as I didn't understand why it couldn't find the ID.

[Heenawter]

Closing. If your ids are mapped as keywords, this should no longer be a problem with the new input controls. If your ids are mapped as numbers, this should be covered by #126795 once it is implemented 👍