Skip to content

Repeated export and import of hive meta store metadata throws artifacts already exists error #289

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
WAG10 opened this issue Oct 3, 2023 · 0 comments

Comments

@WAG10
Copy link

WAG10 commented Oct 3, 2023

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 migration_pipeline.py --export-pipeline --profile oldWS --azure --keep-tasks metastore

  • Once exported, import the same using below command:
    python3 migration_pipeline.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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant