-
Notifications
You must be signed in to change notification settings - Fork 3.7k
[fix](statistics)Fix sample analyze agg/mor table doesn't remove new partition flag bug. #51116
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
Conversation
|
Thank you for your contribution to Apache Doris. Please clearly describe your PR:
|
|
run buildall |
TPC-H: Total hot run time: 33699 ms |
TPC-DS: Total hot run time: 193646 ms |
ClickBench: Total hot run time: 29.02 s |
fe/fe-core/src/main/java/org/apache/doris/statistics/TableStatsMeta.java
Outdated
Show resolved
Hide resolved
|
run buildall |
TPC-H: Total hot run time: 34078 ms |
TPC-DS: Total hot run time: 185761 ms |
ClickBench: Total hot run time: 28.56 s |
|
run p0 |
|
PR approved by at least one committer and no changes requested. |
|
PR approved by anyone and no changes requested. |
zfr9527
left a comment
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
…partition flag bug. (apache#51116) ### What problem does this PR solve? Related PR: apache#49918 Problem Summary: Fix sample analyze agg/mor table doesn't remove new partition flag bug. When a new partition load data for the first time, we set a flag to this table's metadata, this flag indicate that the statistics data of this table is expired and not accurate, so it will trigger a new collection for this table. After collect all columns of this table, we remove this flag so it will not be analyzed again. This pr (apache#49918) skip collecting value columns of agg and unique mor table, but didn't change the logic to remove the new partition flag. The old logic require all columns has been collected before remove the flag, but value columns are skipped, so the flag will never be removed. This will cause the table be analyzed repeatedly. This pr is to fix the bug.
What problem does this PR solve?
Related PR: #49918
Problem Summary:
Fix sample analyze agg/mor table doesn't remove new partition flag bug.
When a new partition load data for the first time, we set a flag to this table's metadata, this flag indicate that the statistics data of this table is expired and not accurate, so it will trigger a new collection for this table. After collect all columns of this table, we remove this flag so it will not be analyzed again.
This pr (#49918) skip collecting value columns of agg and unique mor table, but didn't change the logic to remove the new partition flag. The old logic require all columns has been collected before remove the flag, but value columns are skipped, so the flag will never be removed. This will cause the table be analyzed repeatedly. This pr is to fix the bug.
Release note
None
Check List (For Author)
Test
Behavior changed:
Does this need documentation?
Check List (For Reviewer who merge this PR)