Hi @ypid-geberit,
I think a solution for your use case would be by using a normalizer that is a kind of analyzer for keyword, and it produces a single token at the end. https://www.elastic.co/guide/en/elasticsearch/reference/current/normalizer.html
If you really don't want to use keyword for your use case, in the book Relevant Search by Doug Turnbull and John Berryman, they proposes an interesting solution for that question that are the sentinel tokens. You add tokens in the boundaries of the text even in the ingest as in the search part.
PUT ypid-exact-match-of-text-test
{
"mappings": {
"properties": {
"text": {
"type": "text"
}
}
}
}
POST ypid-exact-match-of-text-test/_doc
{
"text": "SENTINEL_BEGIN You Know, for Search SENTINEL_END"
}
POST ypid-exact-match-of-text-test/_doc
{
"text": "SENTINEL_BEGIN Elastic Stack SENTINEL_END"
}
POST ypid-exact-match-of-text-test/_doc
{
"text": "SENTINEL_BEGIN You Know, for Search (Elastic Stack) SENTINEL_END"
}
The search part would also have the sentinel tokens. In order to match exactly the phase you would have to use match phase query along with boolean queries, like the example below.
GET ypid-exact-match-of-text-test/_search?filter_path=hits.hits._source.text
{
"query": {
"bool": {
"should": [
{
"match_phrase": {
"text": "SENTINEL_BEGIN You Know, for Search SENTINEL_END"
}
},
{
"match_phrase": {
"text": "SENTINEL_BEGIN Elastic Stack SENTINEL_END"
}
}
]
}
}
}