Closed
Description
In languages implemented on top of Elasticsearch, exact matching on text field (non-exact fields) is problematic since the match can happen in a non exact fashion (e.g. a text
field with value "an apple" can match "apple").
Examples of said discussions are mentioned are #52709 and a strategy for coping with this (falling back to keyword
for aggregations and exact comparisons, in SQL, is documented here.
As different languages across the stack (KQL, EQL, SQL) have to deal with this issue, it's worth investigating whether having a generalized approach or even better, support for said strategy in Elasticsearch itself is desirable.