[AMORO-3951] Implement the table merge #4049
Draft
+206
−21
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Why are the changes needed?
Previously, table-level process information was split across two models (
table_process_stateandtable_process), causing duplication. Additionally,TableProcessMeta.processTypeused aStringtype, which lacked type safety. This PR unifies the storage model, introduces type-safeActionobjects, and creates a unified scheduling system for both Optimizing and Maintainer operations.Brief change log
table_process_stateandtable_processinto a single model usingtable_processtableTableProcessMeta.processTypefromStringtoActiontypeOPTIMIZING_MINOR,OPTIMIZING_MAJOR,OPTIMIZING_FULLinIcebergActionsAction2StringConverter: MyBatis TypeHandler for Action ↔ database string conversionTableProcessMapperandProcessServicenow useActiontypeHow was this patch tested?
ActiontypeDocumentation
Does this pull request introduce a new feature? (yes / no)
If yes, how is the feature documented? (not applicable / docs / JavaDocs / not documented)