yihua opened a new pull request, #19426: URL: https://github.com/apache/hudi/pull/19426
### Change Logs Adds `hoodie.meta.sync.force.recreate.table` to `HoodieSyncConfig`. When set to `true`, `HiveSyncTool` always drops and recreates the metastore table via the existing `createOrReplaceTable`/`recreateAndSyncHiveTable` path on every sync of a table that already exists, regardless of whether the incremental sync would otherwise succeed or be a no-op. Today the tool only recreates the table as an error-recovery path (`recreate_table_on_error`) or when the table's stored location drifts from the Hoodie base path; there was no way to force a full resync of table schema/properties on demand. No code was copied. ### Impact New optional config, defaulted to `false`, so no behavior change unless explicitly enabled. When enabled, every sync run of an existing table drops and recreates it (schema, serde/table properties, and partitions) instead of doing an incremental sync. ### Risk level: low Guarded by a new config that defaults to `false`. The recreate path itself (`createOrReplaceTable`) is existing, already-tested code used by `recreate_table_on_error` and the base-path-mismatch case; this change only adds a new trigger for it, shared via a `shouldRecreateTable` helper with the existing base-path-mismatch check. ### Documentation Update Config documentation is included via `withDocumentation(...)` on the new `ConfigProperty`, consistent with how other meta-sync configs are documented. ### Contributor's checklist - [x] Read through [contributor's guide](https://hudi.apache.org/contribute/how-to-contribute) - [x] Change Logs and Impact were stated clearly - [x] Adequate tests were added if applicable - [ ] CI passed -- 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]
