Prepare the Data Catalog physical data layer for Tableau stitching

To stitch data objects in your data sources to their corresponding assets in Collibra Data Intelligence Cloud, the full names of the data objects and assets must match exactly. The full names are constructed according to the full path of the data objects in your data source:

(system name) > database name > schema name > table name > column name

However, when you register a data source via Jobserver or via the lineage harvester, only assets of the following asset types are created in Data Catalog:

  • Schema
  • Table
  • Column

Therefore, you have to create a Database asset and create a relation between it and the Schema asset, to construct the full path hierarchy required for full name matching. If you set the useCollibraSystemName property to true in your lineage harvester configuration file, you also need to create a System asset and create a relation between it and the Database asset. We refer to this as preparing the Data Catalog physical data layer.

Note This topic does not apply if you register a data source via Edge because in that case, Collibra automatically creates the system > database > schema > table > column hierarchy.

For more information, see Automatic stitching and Prepare the lineage harvester configuration file for Tableau.

Important In the global assignment of each asset type included in the TableauPower BI operating model, ensure that none of the characteristics that are in the operating model have a maximum cardinality of “0”. If the maximum cardinality is set to “0” for any such characteristics, ingestion will fail.

Prerequisites

Steps

  1. Register a database as data source.
    After registration, the assets of the following asset types are created in Data Catalog:
    • Schema
    • Table
    • Column
  2. Create a Database asset.
  3. Tip We strongly recommend to use the name as your original data source, so that the name of the Database asset matches Tableau's naming convention.
    1. Open the product for which you want to create an asset (for example, Business Glossary).
    2. On the main toolbar, click .
    3. On the Assets tab, click Database.
      The Create Asset dialog box appears.
    4. Enter the required information.
      FieldDescription
      Type

      The asset type of the asset that you are creating.

      Domain

      The domain to which the asset will belong.

      Tip Ensure that the domain type of the selected domain is assigned to the selected asset type.

      Name

      A name to identify the asset.

      Tip 

      You can simultaneously create multiple assets.
      To do so, after typing the name, press Enter, and then type the next name. Depending on the settings, asset names may need to be unique in their domain. If you enter a name that already exists, it appears in the strike-through style.

    5. Click Create.
      A message stating that one or more assets are created appears in the upper-right corner of the page.
  4. Create a relation between the Database asset and the Schema asset using the Technology Asset has / belongs to Schema relation type.
    1. In the tab pane, click Add Characteristic.
      The Add a characteristic dialog box appears.
    2. Click Relations.
    3. Search for and click has schema.
      The Add has schema dialog box appears.
    4. Enter the required information.
      OptionDescription
      Assets

      The name of the schema.

      Filter suggested assets by organization

      Option to filter the suggestions based on selected communities and domains.

      If this option is selected, the organization tree appears. You can then filter and select domains and communities.

      Start dateOptionally enter the date on which the relation between the assets becomes applicable. Leave this field empty to create a permanent relation.
      End dateOptionally enter the date on which the relation between the assets is no longer applicable. Leave this field empty to create a permanent relation.
    5. Click Save.
  5. Check that the following relations are created for all Column assets that you want to stitch to Tableau assets:
    • Schema contains / is part of Table
    • Column is part of / contains Table

What's next?

Set up the lineage harvester for Tableau ingestion.