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.
An issue occurs when using a custom analyzer I don't know why it behaves differently from the built-in analyzers in Lucene, even though the implementation is the same.
The issue occurs when searching with uppercase letters with wildcard characters. The custom analyzer does not ignore the case sensitivity as expected.
To reproduce the issue:
Instead of using a custom analyzer, I used Lucene's
EnglishAnalyzer
, which is very similar to the custom analyzer we used. The main difference is that the custom analyzer usesDecimalDigitFilter
.I tried to use the exact same filters that the
EnglishAnalyzer
uses, but the same issue persists.Lucene
EnglishAnalyzer
implementation:https://github.com/apache/lucene/blob/2c81649e284b1a1f3a4b46fd589befc87306d0dc/lucene/analysis/common/src/java/org/apache/lucene/analysis/en/EnglishAnalyzer.java#L102-L110
Mandatory checks
CHANGELOG.md
described in a way that is understandable for the average user (if applicable)