-
Notifications
You must be signed in to change notification settings - Fork 3.3k
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.
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
[Feature](topn) BE adaptive choose whether push topn filter down to storage layer #34713
Conversation
Thank you for your contribution to Apache Doris. Since 2024-03-18, the Document has been moved to doris-website. |
run buildall |
TeamCity be ut coverage result: |
TPC-H: Total hot run time: 40599 ms
|
TPC-DS: Total hot run time: 186739 ms
|
PR approved by anyone and no changes requested. |
PR approved by at least one committer and no changes requested. |
…torage layer (apache#34713) support judge topn filter push down topn filter will push down to storage layer when 2 case: filter target is key column table data model is dup/merge on write
…torage layer (apache#34713) support judge topn filter push down topn filter will push down to storage layer when 2 case: filter target is key column table data model is dup/merge on write
Proposed changes
support judge topn filter push down
topn filter will push down to storage layer when 2 case:
Further comments
If this is a relatively large or complex change, kick off the discussion at dev@doris.apache.org by explaining why you chose the solution you did and what alternatives you considered, etc...