Run the migration script

The migration script is triggered by a lineage harvester command. You then use arguments to migrate your customized asset types and custom attribute types and relation types.

Prerequisites

• You have Collibra Data Intelligence Cloud 2022.01 or newer.
  
• You have downloaded lineage harvester version 2022.03 or newer and you have the necessary system requirements to run it.
• You have a global role that has the Manage all resources global permission.
• You have a global role with the Catalog global permission, for example, Catalog Author.
• You have a global role with the Technical lineage global permission.
• You have a global role with the Data Stewardship Manager global permission.
• You have a resource role with the following resource permission on the community level in which you created the BI Data Catalog domain:

  • Asset: Add
  • Attribute: Add
  • Domain: Add
  • Attachment: Add
• You have tested your connectivity with the Tableau server.

Steps

1. Run the following command to start the lineage harvester and trigger the migration:
   • Windows: .\bin\lineage-harvester migrate-tableau <v1_tableau_server_asset_id> <v2_source_id>
     
   • for other operating systems: ./bin/lineage-harvester migrate-tableau <v1_tableau_server_asset_id> <v2_source_id>
2. Use the following arguments to migrate:
   • Customized asset types: -a <customAssetTypeId>
     
   • Custom attribute types: -t <customAttributeTypeId>
     
   • Custom relation types: -r <customRelationTypeId>

   Tip You can migrate multiple asset types, attribute types and relation types by repeating the relevant command. In the following example, two asset types are migrated, one after the other, by repeating the -a command, followed by the relevant ID of each asset type.

./bin/lineage-harvester migrate-tableau 7cc9f692-bbe4-467f-8ffb-f43545465fcf testtableau22 \
  -a asd13io2-sda2-sdi2-jsd9-asdoi124io12 \
  -a ard86co4-sea5-sc4r-hk39-kjsv9she3hs9 \
  -t 3ffafa8e-029c-4d01-a3c9-1c36e43c2655 \
  -r d0086c90-98e6-4782-b07a-40fcb43845a3

What's next?

• The following elements are migrated:
  • Your custom v1 asset types, attribute types and relation types.
  • All assets of your custom v1 asset types.
  • The custom attributes and relations of your custom v1 assets.
  • Any tags that you added to your v1 assets.

• The following elements are ignored during the migration:
  • All assets of out-of-the-box v1 asset types:
    • Their custom attributes and relations, however, are migrated and saved to their respective v2 assets.
    • With the exception of Tableau Data Entity, Tableau Report Attribute and Tableau View assets, which are also ignored, but so too are the attributes and relations of such assets.
  • Any attribute types and relation types that are included in the operating model.

Tip You can check the progress of the migration in Activities.

To refresh the Tableau integration v2 metadata, you can run the lineage harvester again using the full-sync command, or schedule jobs to run them automatically.