Uh oh!
There was an error while loading. Please reload this page.
[fix](external catalog) Distinguish between functions used to refresh cache and change catalog properties - #56639
Conversation
hello-stephen
commented
Sep 29, 2025
Thank you for your contribution to Apache Doris. Please clearly describe your PR:
|
zy-kkk
commented
Sep 29, 2025
run buildall |
doris-robot
commented
Sep 29, 2025
TPC-DS: Total hot run time: 190122 ms |
doris-robot
commented
Sep 29, 2025
ClickBench: Total hot run time: 29.97 s |
hello-stephen
commented
Sep 29, 2025
FE Regression Coverage ReportIncrement line coverage |
morningman
commented
Oct 26, 2025
run buildall |
doris-robot
commented
Oct 26, 2025
ClickBench: Total hot run time: 28 s |
hello-stephen
commented
Oct 26, 2025
FE UT Coverage ReportIncrement line coverage |
hello-stephen
commented
Oct 26, 2025
FE Regression Coverage ReportIncrement line coverage |
morningman
commented
Oct 27, 2025
run buildall |
doris-robot
commented
Oct 27, 2025
ClickBench: Total hot run time: 29.62 s |
hello-stephen
commented
Oct 27, 2025
FE UT Coverage ReportIncrement line coverage |
hello-stephen
commented
Oct 27, 2025
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. |
Uh oh!
There was an error while loading. Please reload this page.
… 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.
hello-stephen
commented
Oct 28, 2025
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)