-
Notifications
You must be signed in to change notification settings - Fork 3.7k
[fix](external catalog) Distinguish between functions used to refresh cache and change catalog properties #56639
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-DS: Total hot run time: 190122 ms |
ClickBench: Total hot run time: 29.97 s |
FE Regression Coverage ReportIncrement line coverage |
8681721 to
86a35e6
Compare
|
run buildall |
ClickBench: Total hot run time: 28 s |
FE UT Coverage ReportIncrement line coverage |
FE Regression Coverage ReportIncrement line coverage |
|
run buildall |
ClickBench: Total hot run time: 29.62 s |
FE UT Coverage ReportIncrement line coverage |
FE Regression Coverage ReportIncrement line coverage |
|
PR approved by at least one committer and no changes requested. |
|
PR approved by anyone and no changes requested. |
… cache and change catalog properties (#56639) The `resetToUninitialized` method should only be called when altering catalog properties, as it resets the entire catalog to an uninitialized state. Previously, `resetToUninitialized` was mistakenly called in `refreshMgr`. Refresh should only refresh the cache, not the entire catalog. Resetting the entire catalog could cause certain clients to shut down during a cache refresh, leading to errors. This PR mainly changes: 1. Change the `onRefreshCache()` method This method will invalid db/table names cache and all meta cache 2. For `refresh` and `hms listener`, only call `onRefreshCache()` 3. For `alter catalog`, call `resetToUninitialized()` TODO: There is still a problem when we `alter catalog`, the ongoing task may be failed or stucked.
… cache and change catalog properties (#56639) The `resetToUninitialized` method should only be called when altering catalog properties, as it resets the entire catalog to an uninitialized state. Previously, `resetToUninitialized` was mistakenly called in `refreshMgr`. Refresh should only refresh the cache, not the entire catalog. Resetting the entire catalog could cause certain clients to shut down during a cache refresh, leading to errors. This PR mainly changes: 1. Change the `onRefreshCache()` method This method will invalid db/table names cache and all meta cache 2. For `refresh` and `hms listener`, only call `onRefreshCache()` 3. For `alter catalog`, call `resetToUninitialized()` TODO: There is still a problem when we `alter catalog`, the ongoing task may be failed or stucked.
FE Regression Coverage ReportIncrement line coverage |
… cache and change catalog properties (apache#56639) The `resetToUninitialized` method should only be called when altering catalog properties, as it resets the entire catalog to an uninitialized state. Previously, `resetToUninitialized` was mistakenly called in `refreshMgr`. Refresh should only refresh the cache, not the entire catalog. Resetting the entire catalog could cause certain clients to shut down during a cache refresh, leading to errors. This PR mainly changes: 1. Change the `onRefreshCache()` method This method will invalid db/table names cache and all meta cache 2. For `refresh` and `hms listener`, only call `onRefreshCache()` 3. For `alter catalog`, call `resetToUninitialized()` TODO: There is still a problem when we `alter catalog`, the ongoing task may be failed or stucked.
What problem does this PR solve?
Issue Number: close #xxx
Related PR: #xxx
Problem Summary:
The
resetToUninitializedmethod should only be called when altering catalog properties, as it resets the entire catalog to an uninitialized state. Previously,resetToUninitializedwas mistakenly called inrefreshMgr. Refresh should only refresh the cache, not the entire catalog. Resetting the entire catalog could cause certain clients to shut down during a cache refresh, leading to errors.This PR mainly changes:
onRefreshCache()methodThis method will invalid db/table names cache and all meta cache
refreshandhms listener, only callonRefreshCache()alter catalog, callresetToUninitialized()TODO:
There is still a problem when we
alter catalog, the ongoing task may be failed or stucked.Release note
None
Check List (For Author)
Test
Behavior changed:
Does this need documentation?
Check List (For Reviewer who merge this PR)