[fix](search) Make AND/OR/NOT operators case-sensitive in search DSL#59747
Merged
airborne12 merged 1 commit intoapache:masterfrom Feb 14, 2026
Merged
[fix](search) Make AND/OR/NOT operators case-sensitive in search DSL#59747airborne12 merged 1 commit intoapache:masterfrom
airborne12 merged 1 commit intoapache:masterfrom
Conversation
Contributor
|
Thank you for your contribution to Apache Doris. Please clearly describe your PR:
|
Member
Author
|
run buildall |
Member
Author
|
run buildall |
TPC-H: Total hot run time: 31207 ms |
Contributor
FE UT Coverage ReportIncrement line coverage `` 🎉 |
Member
Author
|
run buildall |
Member
Author
|
run buildall |
TPC-H: Total hot run time: 28819 ms |
TPC-DS: Total hot run time: 184365 ms |
Member
Author
|
run buildall |
Member
Author
|
run buildall |
Per specification requirement apache#5, only uppercase AND/OR/NOT should be recognized as operators in search DSL. Lowercase and/or/not should be treated as regular terms, causing parse errors when used as operators. Changes: - Update SearchLexer.g4 to only match uppercase keywords - Update unit tests to expect parse errors for lowercase operators - Update regression tests accordingly - Add comprehensive DSL operator test cases Co-Authored-By: Claude Opus 4.5 <[email protected]>
Member
Author
|
run buildall |
TPC-H: Total hot run time: 29555 ms |
TPC-DS: Total hot run time: 182972 ms |
Contributor
|
PR approved by at least one committer and no changes requested. |
Contributor
|
PR approved by anyone and no changes requested. |
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
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.
What problem does this PR solve?
Issue Number: close #xxx
Related PR: #59394
Problem Summary:
The search DSL should only recognize uppercase
AND,OR,NOTas boolean operators in search lucene boolean mode. Previously, lowercaseand,or,notwere also treated as operators, which does not conform to the specification.This PR makes the boolean operators case-sensitive:
AND,OR,NOTare recognized as operatorsand,or,notare now treated as regular search termsRelease note
Make search DSL boolean operators (AND/OR/NOT) case-sensitive in lucene boolean mode.
Check List (For Author)
Test
Behavior changed:
and,or,notare no longer recognized as operators in search DSL. Users must use uppercaseAND,OR,NOT.Does this need documentation?
Check List (For Reviewer who merge this PR)