-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
[BugFix] clean stale column stats periodically (backport #45839) #46152
Conversation
Cherry-pick of 1e4bd06 has failed:
To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally |
@mergify[bot]: Backport conflict, please reslove the conflict and resubmit the pr |
) Signed-off-by: packy92 <[email protected]>
) Signed-off-by: packy92 <[email protected]>
bc48608
to
1a412b2
Compare
|
|
Why I'm doing:
Truncate operation didn't clear the stale column statistics.
What I'm doing:
OlapTable.dropPartition()
interface leads it will be processed in follower replay operation. So move it to the outer process to ensure it only be processed in leader.Fixes #issue
What type of PR is this:
Does this PR entail a change in behavior?
If yes, please specify the type of change:
Checklist:
Bugfix cherry-pick branch check:
This is an automatic backport of pull request #45839 done by [Mergify](https://mergify.com). ## Why I'm doing: Truncate operation didn't clear the stale column statistics.
What I'm doing:
OlapTable.dropPartition()
interface leads it will be processed in follower replay operation. So move it to the outer process to ensure it only be processed in leader.Fixes #issue
What type of PR is this:
Does this PR entail a change in behavior?
If yes, please specify the type of change:
Checklist: