j1wonpark opened a new pull request, #4076: URL: https://github.com/apache/amoro/pull/4076
## Why are the changes needed? When the `self-optimizing.group` property of a table is changed (either directly or through catalog default settings), the `group_name` column in the `table_runtime` database table is not updated during table refresh. This causes: 1. Tables remain bound to the old optimizer group even after configuration changes 2. `handleConfigChanged()` uses stale `group_name` from DB for queue binding 3. Tables get stuck in `pending` status permanently when the original optimizer group no longer exists **Root Cause:** `DefaultTableRuntime.refresh()` method was missing `updateGroup()` call in the store transaction. ## Brief change log - **DefaultTableRuntime.java**: Added `updateGroup(g -> newGroupName)` call in `refresh()` method to update the `group_name` column in DB when optimizer group changes - **TestDefaultTableRuntimeHandler.java**: Added `testRefreshUpdatesOptimizerGroup()` test to verify that `getGroupName()` returns the new group name after refresh ## How was this patch tested? - [x] Add some test cases that check the changes thoroughly including negative and positive cases if possible - [ ] Add screenshots for manual tests if appropriate - [x] Run test locally before making a pull request ## Documentation - Does this pull request introduce a new feature? **no** - If yes, how is the feature documented? **not applicable** -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
