-
Notifications
You must be signed in to change notification settings - Fork 3.4k
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
[fix](analyze) correct duplicated counting of updated rows for mv in cloud mode #33136
Conversation
Thank you for your contribution to Apache Doris. Since 2024-03-18, the Document has been moved to doris-website. |
PR approved by anyone and no changes requested. |
clang-tidy review says "All clean, LGTM! 👍" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
run buildall |
3a30756
to
78b0bc8
Compare
run buildall |
clang-tidy review says "All clean, LGTM! 👍" |
TPC-H: Total hot run time: 39272 ms
|
TPC-DS: Total hot run time: 181856 ms
|
ClickBench: Total hot run time: 31.04 s
|
Load test result on machine: 'aliyun_ecs.c7a.8xlarge_32C64G'
|
…cloud mode Signed-off-by: freemandealer <freeman.zhang1992@gmail.com>
78b0bc8
to
369edab
Compare
run buildall |
clang-tidy review says "All clean, LGTM! 👍" |
TPC-H: Total hot run time: 38562 ms
|
TPC-DS: Total hot run time: 182598 ms
|
ClickBench: Total hot run time: 30.38 s
|
Load test result on machine: 'aliyun_ecs.c7a.8xlarge_32C64G'
|
run feut |
1 similar comment
run feut |
run buildall |
clang-tidy review says "All clean, LGTM! 👍" |
TPC-H: Total hot run time: 39457 ms
|
TPC-DS: Total hot run time: 182520 ms
|
ClickBench: Total hot run time: 31.54 s
|
Load test result on machine: 'aliyun_ecs.c7a.8xlarge_32C64G'
|
run feut |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Proposed changes
Issue Number: close #xxx
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...