-
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
[Opt](Iceberg) handle count pushdown in fe side #34928
Merged
morrySnow
merged 1 commit into
apache:master
from
zhangbutao:handle_iceberg_count_in_fe
May 17, 2024
Merged
[Opt](Iceberg) handle count pushdown in fe side #34928
morrySnow
merged 1 commit into
apache:master
from
zhangbutao:handle_iceberg_count_in_fe
May 17, 2024
Conversation
This file contains 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
Thank you for your contribution to Apache Doris. Since 2024-03-18, the Document has been moved to doris-website. |
cc @morningman |
zhangbutao
force-pushed
the
handle_iceberg_count_in_fe
branch
from
May 15, 2024 13:29
d08ddcc
to
a0c7838
Compare
run buildall |
TPC-H: Total hot run time: 40857 ms
|
TPC-DS: Total hot run time: 186375 ms
|
ClickBench: Total hot run time: 30.43 s
|
run buildall |
zhangbutao
force-pushed
the
handle_iceberg_count_in_fe
branch
2 times, most recently
from
May 16, 2024 02:26
20824cd
to
0fbe478
Compare
run buildall |
zhangbutao
force-pushed
the
handle_iceberg_count_in_fe
branch
from
May 16, 2024 02:33
0fbe478
to
76ce0ef
Compare
run buildall |
924060929
approved these changes
May 17, 2024
github-actions
bot
added
the
approved
Indicates a PR has been approved by one committer.
label
May 17, 2024
PR approved by at least one committer and no changes requested. |
PR approved by anyone and no changes requested. |
morrySnow
approved these changes
May 17, 2024
dataroaring
pushed a commit
that referenced
this pull request
May 26, 2024
Iceberg count can be regarded as metadata operation, and this can be done in fe side. So we need to pass count push down to fe as well as no need to initialize iceberg spilits. This optimization can reduce lots of time when dealing with iceberg count statement.
yiguolei
pushed a commit
that referenced
this pull request
Jul 16, 2024
morningman
pushed a commit
that referenced
this pull request
Aug 2, 2024
## Proposed changes related #34928
dataroaring
pushed a commit
that referenced
this pull request
Aug 11, 2024
## Proposed changes related #34928
dataroaring
pushed a commit
that referenced
this pull request
Aug 16, 2024
## Proposed changes related #34928
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
approved
Indicates a PR has been approved by one committer.
dev/2.1.5-merged
dev/3.0.0-merged
reviewed
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.
Proposed changes
Iceberg
count
can be regarded as metadata operation, and this can be done in fe side. So we need to pass count push down to fe as well as no need to initialize iceberg spilits.This optimization can reduce lots of time when dealing with iceberg
count
statement.Issue Number: close #xxx
Further comments
If this is a relatively large or complex change, kick off the discussion at [email protected] by explaining why you chose the solution you did and what alternatives you considered, etc...