- Via Edge (Beta).
- Via the Data Catalog user interface.
- Via the lineage harvester, as described in this section of the documentation.
This topic describes the features and limitations of using the lineage harvester to create Tableau assets and data in Data Catalog.
The Tableau operating model associated with this integration method is only available in Collibra versions 2021.10 and newer.
Warning As of October 2022, Tableau is enforcing multi-factor authentication for Tableau Cloud Admin users. However, the lineage harvester doesn’t support multi-factor authentication. Therefore, Tableau Cloud users with an Admin role must use token-based authentication. This does not affect Tableau Server users or Tableau Cloud users with an Explorer role.
Important Data Catalog uses Tableau's REST API to get metadata information and follows Tableau's requirements regarding authentication methods. As such, you need a Tableau user with access to the relevant Tableau sites. For more information, see the Tableau documentation.
Features
| Feature | Integration via Data Catalog UI | Integration via the lineage harvester |
|---|---|---|
| Catalog ingestion |
|
|
| Technical lineage |
|
|
| Automatic stitching |
|
|
| Embedded data source connectivity |
|
|
| Custom SQL parsing |
|
|
| On-prem credential storage |
|
|
| Ingestion via Explorer role (with the Data Management Add-On) |
|
Limitations
Currently, there are still a few limitations to integrating Tableau metadata via the lineage harvester:
- You ingest Tableau via the lineage harvester, instead of via the Data Catalog UI. All changes to the Tableau ingestion must be configured in the lineage harvester configuration file, instead of Data Catalog.
- The Stitch button is part of the legacy Tableau integration (via Data Catalog) and does not work when integrating Tableau via the lineage harvester, as stitching is done automatically via this method.
- We partially support Unions and Joins. For example, Unions created via the Tableau UI are not represented in Data Catalog. Tableau Data Sources created via custom SQL are supported.
- Hidden Tableau worksheets are currently ingested in Collibra. You can find them by filtering on the attribute “Visible on server”, which has the value "false".
- Data fields are ingested with their actual names. Labels and aliases are not returned by the APIs.