You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Fix issue with migrating MANAGED hive_metastore table to UC (#2928)
<!-- REMOVE IRRELEVANT COMMENTS BEFORE CREATING A PULL REQUEST -->
## Changes
HMS MANAGED tables when deleted also delete their underlying data.
If an HMS-managed table is migrated to UC as EXTERNAL, dropping the HMS
table will delete the underlying data file and render the UC table
unusable, leading to a non-recoverable data loss.
Changing the MANAGED table to EXTERNAL may have consequences on
regulatory data cleanup, as deleting the EXTERNAL table no longer
deletes the underlying table. It would cause leakage of data when tables
are dropped.
As with the case of duplicating the data, if new data is added to either
HMS or UC, the other table goes out of sync requiring re-migration
Resolves#2838
### Functionality
- [ ] added relevant user documentation
- [ ] modified existing workflow: `...`
### Tests
<!-- How is this tested? Please see the checklist below and also
describe any other relevant tests -->
- [ ] added unit tests
- [ ] added integration tests
"Migrate MANAGED HMS table as EXTERNAL UC table. This option would require you to convert MANAGED HMS tables to EXTERNAL HMS tables once UC migration is complete, otherwise deleting HMS MANAGED table would delete the migrated UC table": 'SYNC_AS_EXTERNAL',
381
381
"Copy data from MANAGED HMS to MANAGED UC table": 'CLONE',
382
+
"Convert MANAGED HMS table to EXTERNAL HMS table and migrate as EXTERNAL UC table. This risks data leakage, as once the relevant HMS tables are deleted, the underlying data won't get deleted anymore.": 'CONVERT_TO_EXTERNAL',
0 commit comments