Closed stratoula closed 17 hours ago
Pinging @elastic/kibana-esql (Team:ESQL)
Pinging @elastic/kibana-data-discovery (Team:DataDiscovery)
My main concern for this is that I am not sure how easy is to detect that a field is a multivalue one
@stratoula would it work to just check if the field value is an array, or does that oversimplify it?
We will see 😄
I looked into it and:
FROM kibana_sample_data_ecommerce | WHERE `category.keyword`=="Women's Clothing" AND `category.keyword`=="Women's Shoes"
this won't return the document with the array value: [Women's Accessories, Women's Clothing]
because multivalue filtering is not supported yet from ES side.
I think for now we should not allow the filtering for multivalue fields
I can make the appendWhereClauseToESQLQuery
to return undefined for multivalue fields.
This means that:
We could make it smarter and hide the cell actions in case of multivalues but @davismcphee I am not super familiar with this piece of code and from a quick glance is not straight forward. I will open a PR with the behavior described above and you can follow up if you wish
Most possibly this behavior will be supported from full text search (QSTR function) which is going to be on snapshot releases quite soon so hopefully in 8.17 will be on GA and we could use it here.
~Wouldn't ... | WHERE field IN ["Women's Accessories", "Women's Clothing"]
work?~
Edit: Never mind I see now that you want an and
Also the query above fails :)
We disabled it in table, chart, fields list and doc viewer. So I am closing it (I will create an ER to enable it when match function is on GA)
Kibana version: 8.15+
Describe the bug:
It creates the wheer clause:
which is invalid
You can replicate by clicking the table cell for the category
The correct filter is
My main concern for this is that I am not sure how easy is to detect that a field is a multivalue one