"{name}" is a text field with no keyword sub...

Warnings reference › source.elasticsearch.analyzed.*

Identifier

source.elasticsearch.analyzed.*

Raised by

The grid (core)

Since

1.77.0

What happened

A text field holds analysed words, not a whole value, and this one has no keyword sub-field to compare against instead. The filter is still pushed - as match_phrase, match_phrase_prefix or a per-word wildcard - because refusing it would fail the grid, but a word match is a different question from the grid's substring or equality test, so the difference is named once per field.

The fix

Give the field a keyword sub-field in the index mapping (the default dynamic mapping already adds .keyword), or leave that column's filter to the grid.

The smallest fix

"message": { "type": "text", "fields": { "keyword": { "type": "keyword" } } }

Reference

Covered in full at the API reference.