This repository was archived by the owner on Nov 7, 2025. It is now read-only.
Fix Lucene query behavior (match operator) #1426
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.
Lucene syntax is not expected to behave the way Quesma handles it.
Using default text fields, for query like:
myText: getAccit is going to perform case-insensitive, exact match.This became apparent when playing with Grafana


but also applies to Kibana when switching to Lucene query language.
We still do not fully implement Lucene syntax translation, but this definitely brings us closer by at least matching the default behavior.
Useful notes for reproducing this situation 👇
Load data
curl -X POST "http://localhost:8080/_bulk"
-H "Content-Type: application/x-ndjson"
--data-binary "@data.ndjson"