Skip to content

[feature](point query) Support IN predicate in short-circuit point query#61650

Open
rnb-tron wants to merge 1 commit intoapache:masterfrom
rnb-tron:in_predicate_short_circuit
Open

[feature](point query) Support IN predicate in short-circuit point query#61650
rnb-tron wants to merge 1 commit intoapache:masterfrom
rnb-tron:in_predicate_short_circuit

Conversation

@rnb-tron
Copy link
Contributor

What problem does this PR solve?

Issue Number: close #xxx

Related PR: #xxx

Problem Summary:
Doris short-circuit point query is a high-performance optimization for MOW (Merge-On-Write) UNIQUE KEY tables. Before this PR, short-circuit point query only matched EqualTo predicates on key columns.

Solution:
Extend short-circuit point query to accept IN predicates on key columns, for both literal values and prepared statement placeholders.

Release note

None

Check List (For Author)

  • Test

    • Regression test
    • Unit Test
    • Manual test (add detailed scripts or steps below)
    • No need to test or manual test. Explain why:
      • This is a refactor/code format and no logic has been changed.
      • Previous test can cover this change.
      • No code files have been changed.
      • Other reason
  • Behavior changed:

    • No.
    • Yes.
  • Does this need documentation?

    • No.
    • Yes.

Check List (For Reviewer who merge this PR)

  • Confirm the release note
  • Confirm test cases
  • Confirm document
  • Add branch pick label

@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?

@rnb-tron
Copy link
Contributor Author

run buildall

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.

2 participants