Add SQL as an optional search language in the query bar

[alexfrancoeur]

SQL queries are great because Dev and Ops already know the syntax, it will be great if they can use the SQL to filter documents from the "Discover" search page or anywhere else the global query bar is present.

Linking to #29215 because this feature is explicitly mentioned here as well.

[elasticmachine]

Pinging @elastic/kibana-app

[elasticmachine]

Pinging @elastic/kibana-app-arch

[stacey-gammon]

or anywhere else the global query bar is present.

I think actually this doesn't make sense on Dashboard, but if you disagree, let me know how you think the UX would go. e.g. your visualization on a dashboard is using the output of the query bar to filter the aggregations it's requesting, SQL is totally different - it's not just used to filter data, it's used to get data, that might be aggregated and not even associated with any actual fields in ES.

it'd be interesting in Discover though, and I could see visualizations created that way.

[felix-lessoer]

We already have prospects / customers asking about this. They "would like to define the amount of data to be displayed for each visualization type using SQL statements" ..

[stacey-gammon]

I'm going to close this in favor of #55842. We have decided not to support SQL as an additional option in the query bar because of it's ability to include aggregations. It may make sense in discover or visualize, but it doesn't make sense in dashboard. We do want to expose additional query languages, just not in the query bar, likely as "data source options" through a different UX.