Ashwin P Chandran

The current implementation is a combo box. @shanilpa is working on the future iteration of the datasource selector. He is the best person to ask this question to :)

Yes, a index pattern cannot be created before an index with that pattern exists. Why are we trying to create an index pattern before the index itself?

@SebastianThorn Can you explain what you mean by > The search patterns don't have an easy "drop-down" or search-function A built-in search or select would make this easier.

@SebastianThorn still a little confused here. Sorry if i sound like im repeating myself. There are two search inputs on the discover page. Which one are you referring to. Also...

Ah i see what you mean. This is already possible. However you have to index the field as a keyword and not a text field. See the example here: https://playground.opensearch.org/app/data-explorer/discover#?_a=(discover:(columns:!(_source),isDirty:!f,sort:!()),metadata:(indexPattern:ff959d40-b880-11e8-a6d9-e546fe2bba5f,view:discover))&_g=(filters:!(),refreshInterval:(pause:!t,value:0),time:(from:now-15m,to:now))&_q=(filters:!(),query:(language:kuery,query:''))...

The DQL query under the hood is converted into a DSL request like below. Are you able to able to query using DSL the fields with `$` in them? ```json...

Nope, thi was useful @markusg80. Adding more context here. To reproduce the issue with DQL search queries involving the $ character, follow these steps: Open the Dashboards Console app and...

So you are able to search with $ in te query bar. So it looks like there is some other issue here. Whats your original index mapping for the problematic...

@minjiewang29 Thanks for opening this issue. Since the first of your two issues is being tracked in #4780 Do you mind if we repurpose this issue to track the other...

@bbarani This is a good issue to bring up and would like to know from product/UX how we should handle something like this. what Bharani describes is a behavior that...