Skip to content

branch-4.0: [opt](hive) use binary search to prune hive partitions #58877 #58921

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Merged
yiguolei merged 1 commit into from
Dec 12, 2025
Merged

branch-4.0: [opt](hive) use binary search to prune hive partitions #58877 #58921

yiguolei merged 1 commit into from
Dec 12, 2025

Conversation

@github-actions
Copy link
Contributor

@github-actions github-actions bot commented Dec 10, 2025

Cherry-picked from #58877

@zy-kkk
[opt](hive) use binary search to prune hive partitions (#58877)
5003198 
Followup #44586
Enable binary search partition pruning optimization for Hive external
tables.

This PR adds binary search partition pruning support for Hive tables by:
- Adding `getSortedPartitionRanges()` method to `ExternalTable` base
class
- Maintaining sorted partition ranges directly in `HivePartitionValues`
for cache lifecycle consistency
- Overriding `getSortedPartitionRanges()` in `HMSExternalTable` to
provide sorted ranges

  **Performance improvement (20000 partitions, 1000 queries):**
  - Binary search enabled: **4.548 seconds**
  - Binary search disabled: **12.849 seconds**
  - **~2.8x faster**
@github-actions github-actions bot requested a review from yiguolei as a code owner December 10, 2025 16:14
@hello-stephen
Copy link
Contributor

hello-stephen commented Dec 10, 2025

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 Dec 10, 2025
@hello-stephen
Copy link
Contributor

hello-stephen commented Dec 10, 2025

run buildall

@hello-stephen
Copy link
Contributor

hello-stephen commented Dec 10, 2025

FE UT Coverage Report

Increment line coverage 60.00% (33/55) 🎉
Increment coverage report
Complete coverage report

@github-actions github-actions bot added the approved Indicates a PR has been approved by one committer. label Dec 12, 2025
@github-actions
Copy link
Contributor Author

github-actions bot commented Dec 12, 2025

PR approved by at least one committer and no changes requested.

@github-actions
Copy link
Contributor Author

github-actions bot commented Dec 12, 2025

PR approved by anyone and no changes requested.

@yiguolei yiguolei merged commit 99ea4a8 into branch-4.0 Dec 12, 2025
24 of 27 checks passed
@github-actions github-actions bot deleted the auto-pick-58877-branch-4.0 branch December 12, 2025 01:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@yiguolei yiguolei yiguolei approved these changes

Assignees

No one assigned

Labels

approved Indicates a PR has been approved by one committer. reviewed

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

5 participants

@hello-stephen @yiguolei @dataroaring @zy-kkk