[KQL] Use term queries for keyword fields #143599
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Prior to this PR, a KQL query like
agent.type: filebeat
would generate amatch
query, regardless of the field type, even thoughmatch
andmatch_phrase
queries are considered full-text (not term-level) queries. This worked forkeyword
fields, because internally in Elasticsearch,match
andmatch_phrase
queries are rewritten asterm
queries.This PR updates the behavior to generate a
term
query instead. This is one step toward adding support for case-insensitive searches on keyword fields.Checklist