Hi Team,
We are facing issue as artifacts already exists error on hive meta store metadata export/import
Steps to replicate:
Create some internal managed tabled in primary workspace
Export the metastore tables using below command:
_python3 migrationpipeline.py --export-pipeline --profile oldWS --azure --keep-tasks metastore
Once exported, import the same using below command:
_python3 migrationpipeline.py --import-pipeline --profile newWS --azure --keep-tasks metastore --session
This will import the hms metadata, Now repeat the same process again
this time we get error during import as tables already exists.
_2023-10-03,07:24:01;INFO;Importing table default.employee
2023-10-03,07:24:04;ERROR;AnalysisException: Table default.employee already exists
2023-10-03,07:24:04;INFO;Importing table default.orders_features
2023-10-03,07:24:04;ERROR;AnalysisException: Table default.orders_features already exists_
Same happens for even update too when we update the already exported table in primary and export it again, Expectation is that it should always import it even if we have the table in secondary so that updates can be posted to the hms metadata
Hi Team, We are facing issue as artifacts already exists error on hive meta store metadata export/import
Steps to replicate:
Create some internal managed tabled in primary workspace
Export the metastore tables using below command: _python3 migrationpipeline.py --export-pipeline --profile oldWS --azure --keep-tasks metastore
Once exported, import the same using below command:
_python3 migrationpipeline.py --import-pipeline --profile newWS --azure --keep-tasks metastore --session
This will import the hms metadata, Now repeat the same process again
this time we get error during import as tables already exists. _2023-10-03,07:24:01;INFO;Importing table default.employee 2023-10-03,07:24:04;ERROR;AnalysisException: Table default.employee already exists 2023-10-03,07:24:04;INFO;Importing table default.orders_features 2023-10-03,07:24:04;ERROR;AnalysisException: Table default.orders_features already exists_
Same happens for even update too when we update the already exported table in primary and export it again, Expectation is that it should always import it even if we have the table in secondary so that updates can be posted to the hms metadata