Skip to content

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

Description

@WAG10

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

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions