fix(lucene): normalize prefix and wildcard queries - #458
Merged
Conversation
lszskye
force-pushed
the
fix_lucene_index_prefix_wildcard
branch
from
July 29, 2026 12:04
1855de9 to
a0fc3f6
Compare
lszskye
force-pushed
the
fix_lucene_index_prefix_wildcard
branch
from
July 30, 2026 02:58
4af7c65 to
aece44c
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Purpose
Fix case-sensitive query mismatches in the Lucene full-text index.
Lucene normalizes alphanumeric tokens to lowercase when building the index, but PREFIX and WILDCARD queries previously used the original query text directly. As a result, queries could not match indexed lowercase terms.
This change:
PREFIX Query;WILDCARD Querywhile preserving*and?;Tests
Generative AI tooling
Generated-by: Codex (GPT-5)