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
Migrating from v1 of hms-mirror to v2 found that --reset-to-default-location doesn't reset the table's location to default to DB's external location in v2.
checked that table is external
checked that DB's location is e.g. /warehouse/tablespaces/external/hive/foo.db
source table has /data/foo/bar and RIGHT's create table statement also has /data/foo/bar instead of /warehouse/tablespaces/external/hive/foo.db/bar
Checked with --global-location-map and mapping worked.
related command options used are:
--data-strategy SQL \
--database foo --table-filter bar \
--reset-to-default-location
Sharing logs privately...
The text was updated successfully, but these errors were encountered:
Tested --translation-type ALIGNED and works as expected (on 19.7 with the HDP3 LOC/MNGDLOC fix).
Waiting for the enhanced GLM logic for the source=target support.
dstreev
added a commit
to dstreev/hms-mirror
that referenced
this issue
Jan 24, 2025
BETA Iceberg conversion support for the STORAGE_MIGRATION data strategy. See [Iceberg Conversion](hms-mirror-iceberg_migration.md) for more details.
**Bugs (Fixed)**
[Add to connection init the ability to set the queue AND trigger an engine resource](cloudera-labs/hms-mirror#173)
[cloudera-labs/hms-mirror#168
Validate SQL elements before making changes to the Cluster](cloudera-labs/hms-mirror#168)
[Extend the HS2 connection validation with Tez task validation](cloudera-labs/hms-mirror#167)
[The reset-to-default-location doesn't seem to be working in v2](cloudera-labs/hms-mirror#165)
Migrating from v1 of hms-mirror to v2 found that --reset-to-default-location doesn't reset the table's location to default to DB's external location in v2.
Checked with --global-location-map and mapping worked.
related command options used are:
Sharing logs privately...
The text was updated successfully, but these errors were encountered: