Skip to content

branch-4.0: [fix](search) Make AND/OR/NOT operators case-sensitive in search DSL #59747#60773

Open
github-actions[bot] wants to merge 1 commit intobranch-4.0from
auto-pick-59747-branch-4.0
Open

branch-4.0: [fix](search) Make AND/OR/NOT operators case-sensitive in search DSL #59747#60773
github-actions[bot] wants to merge 1 commit intobranch-4.0from
auto-pick-59747-branch-4.0

Conversation

@github-actions
Copy link
Contributor

Cherry-picked from #59747

…59747)

### What problem does this PR solve?

Issue Number: close #xxx

Related PR: #59394

Problem Summary:
The search DSL should only recognize uppercase `AND`, `OR`, `NOT` as
boolean operators in search lucene boolean mode. Previously, lowercase
`and`, `or`, `not` were also treated as operators, which does not
conform to the specification.

This PR makes the boolean operators case-sensitive:
- Only uppercase `AND`, `OR`, `NOT` are recognized as operators
- Lowercase `and`, `or`, `not` are now treated as regular search terms
- Using lowercase operators in DSL will result in a parse error

### Release note

Make search DSL boolean operators (AND/OR/NOT) case-sensitive in lucene
boolean mode.
@github-actions github-actions bot requested a review from yiguolei as a code owner February 15, 2026 14:06
@hello-stephen
Copy link
Contributor

Thank you for your contribution to Apache Doris.
Don't know what should be done next? See How to process your PR.

Please clearly describe your PR:

  1. What problem was fixed (it's best to include specific error reporting information). How it was fixed.
  2. Which behaviors were modified. What was the previous behavior, what is it now, why was it modified, and what possible impacts might there be.
  3. What features were added. Why was this function added?
  4. Which code was refactored and why was this part of the code refactored?
  5. Which functions were optimized and what is the difference before and after the optimization?

@dataroaring dataroaring reopened this Feb 15, 2026
@hello-stephen
Copy link
Contributor

run buildall

@hello-stephen
Copy link
Contributor

FE UT Coverage Report

Increment line coverage `` 🎉
Increment coverage report
Complete coverage report

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants

Comments