KQL everywhere

[rayafratkina]

Describe the feature:
If KQL is the default search experience, as a user I would either expect it to be the default or at least an option everywhere else. Some examples off the cuff include

• KQL in filter aggregations KQL + autocomplete in filter aggregation  #29790
• TSVB filters
• any others?

[elasticmachine]

Pinging @elastic/kibana-app

[rayafratkina]

This may not be easy since there is currently no way to distinguish query language in TSVB. We can probably use the same approach we used before: if the saved search is a text string, assume it's Lucene.

Note a top priority right now.

[AlonaNadler]

We can probably use the same approach we used before: if the saved search is a text string, assume it's Lucene.

It wouldn't be exactly the same, users either use saved searches in a dashboard, in visualize or just open it in Discover. The concern with TSVB and Visualize filter aggregation is different, users often copy paste their search bar query into the filter aggregations, in that case, they will get errors. We are adding indications in the query bar but not in filter aggregation.
Short term resolution is to add placeholder text in the filter aggregation Lucene, as a temporary solution, otherwise users can start troubleshooting for a while until realize what is the issue

[timroes]

Closing this now, since we have KQL enabled in all significant places.