Indication of the search language currently used (KQL, Lucene)

[AlonaNadler]

Currently, users need to go to the options next to the search bar in order to switch between KQL and Lucene, it is also the only way to know which language they are currently using.

Describe the feature: As preparation for moving to use KQL by default, add an indication visible in the search bar to whether the search bar is using KQL or Lucene without the need to select options link

@elastic/kibana-design

[elasticmachine]

Pinging @elastic/kibana-app

[cchaos]

Currently the placeholder text looks like:

For both KQL and Lucene.

You could just change it to lead in with KQL search... and Lucene search....

Also we might want to decrease the footprint of the options link and use a gear icon instead.

[AlonaNadler]

Can we somehow place it next to the options link to make it more actionable, currently options is the place to switch between this too, it might be more descriptive that way

[Bargs]

@cchaos another thing I just thought of is if we only put it in the placeholder, there will still be no visual indication of which language is in use when the input is already populated with text (e.g. loading a saved search)

[AlonaNadler]

This morning I spoke with a user who wasn't aware he was using KQL and was pasting the search bar query into filter aggregation (Lucene) without luck or understanding what is wrong.
We might need to be explicit in the filter aggregation that it is only using Lucene

[Bargs]

If we used the gear icon and got rid of the "options" text there would be some space to make the language name part of the button itself. What does everyone think of something like this?

[AlonaNadler]

@Bargs good idea I'm good with the plan 👍

[cchaos]

My only concern is how much space we're losing in the query bar for that toggle (which really will probably only be clicked once).

if we only put it in the placeholder, there will still be no visual indication of which language is in use when the input is already populated with text (e.g. loading a saved search)

Wouldn't they be able to tell by the syntax?

[Bargs]

@cchaos the syntax is almost identical in most cases. For example response:200 AND extension:jpg is a valid query in both lucene and KQL.

[snide]

If KQL is the new default, I'd drop the extranous first icon (it serves no purpose). I'd remove the placeholder text, which isn't needed now that KQL explains the syntax. I'd then just make "options" into the name of the active syntax language ("KQL" for default). You'll get extra room with the removal of the icon and KQL will likely always be the case these days, so you'll gain some space there as well.

I don't think most people know what "e.g" means, and the extra parens needed make it confusing to know what part of that placeholder is real syntax and what isn't. I think it's better to just let people learn it through KQL autocomplete since it does a great job of showing you the ropes.

[Bargs]

@snide the only snag there is that autocomplete only works with a Basic license or above.

[Bargs]

Put up a PR with Dave's suggestions #30899