Filter value suggestions takes long time to load

[AlonaNadler]

Describe the feature:
Filter suggestions are extremely helpful, however value suggestions can take a long time to load

The query to load the drop-down appears to
(a.) draw from all records that match the index filter (regardless of the filtered time range)
(b.) it doesn’t cache these records; repeat visits to the same dropdown engender further delay.

suggestion: Filter suggestions should take into consideration the filters already applied (time range, other filters currently applied)

Also, can client-side caching help? with repeat visits? cc: @timroes / @nreese

[elasticmachine]

Pinging @elastic/kibana-app-services (Team:AppServices)

[Dosant]

Looks like the feedback comes from 7.10.2?

• Since 7.11 we are adding a time range filter, so queries should be faster: [Autocomplete] Support useTimeFilter option #81515
• In future we will use a new autocomplete API that will replace terms aggregation for suggestions in Kibana: [Autocomplete] Integrate new autocomplete API #92783 cc @lizozom @elastic-jb

[lizozom]

@Dosant We're not filtering value suggestions by time range, only the autocomplete suggestions. Imagine what would happen if you:

1. Set a filter
2. Change the timerange
3. Edit the filter

The filter would appear broken and if you make a mistake, you might not be able to change the value back, if you don't re-adjust the time range.

I think users still need a reliable way to get a full, exhaustive list of possible values (maybe with the exception of cold storage), and even the new autocomplete API wouldn't be able to help with that (as it's not an exhaustive API).

[Dosant]

@lizozom, thanks, looks like I missed the difference between KQL autocomplete and filter value suggestions mentioned in this issue 🤦‍♂️

[lizozom]

Should be resolved by #92783 (combining an autocomplete API call without any term string with some kind of a UI indication to show that results are incomplete)

[nreese]

Should be resolved by #92783 (combining an autocomplete API call without any term string with some kind of a UI indication to show that results are incomplete)

#92783 is targeting 7.14.0. This issue is a blocker for 7.13.0. What can we do in 7.13.0 to fix this problem?

[nreese]

Disregard last comment. Cross posted from another issue. Sorry for the noise