Lineage 1 Download
Gertrudis Paronto
Knowing where your data comes from is key to trusting the data, and knowing who else uses it means you can analyze the impact of changes to data in your environment. The lineage feature in Tableau Catalog helps you do both these things.
When you have a Data Management license and Tableau Catalog enabled, you have access to lineage information for your content. For more information about Tableau Catalog, see "About Tableau Catalog" in the Tableau Server(Link opens in a new window) or Tableau Cloud(Link opens in a new window) Help.
Lineage shows dependencies in relationship to the lineage anchor, which is the asset selected. A lineage anchor can be a database, table, workbook, published data source, virtual connection, virtual connection table, lens, metric, or flow. (In the image above, the anchor is the "Orders (superstore)"data source, and in the image below, the anchor is the "Batters" table.) All the assets below the anchor depend, either directly or indirectly, on the anchor and are called outputs or downstream assets. The assets above the anchor are the assets the anchor is either directly or indirectly dependent on and are called inputs or upstream assets.
Starting in Tableau Cloud June 2023 and Tableau Server 2023.3, lineage pages for data sources include search and filtering (in the top-right of the fields list) that allow you to quickly find fields of interest or relevance.
When you select a field in a data source or a column in a table, the lineage is filtered to show only downstream assets that depend on the field (or column) or upstream inputs to the field (or column) as in this 'Superstore' workbook example that shows the lineage filtered for the Commission (Variable) field:
Cube data sources (also known as multidimensional or OLAP data sources) are not supported by Tableau Catalog. Tableau content (such as a data source, view, or workbook) that relies on cube data does not display any cube metadata or cube lineage in Catalog.
When metadata is blocked because of limited permissions, or the asset is in a Personal Space, Catalog still counts the workbook. But instead of seeing some of the sensitive metadata, you see Permissions required. For more information, see Access lineage information.
Amazon SageMaker supports tracking lineage entities from a different AWS account. Other AWS accounts can share their lineage entities with you and you can access these lineage entities through direct API calls or SageMaker lineage queries.
You can group and share your Lineage Tracking Entities through a lineage group in Amazon SageMaker. SageMaker supports only one default lineage group per account. SageMaker creates the default lineage group whenever a lineage entity is created in your account. Every lineage entity owned by your account is assigned to this default lineage group. To share lineage entities with another account, you share this default lineage group with that account.
In addition to SageMaker automatically creating lineage entities, if you have cross-account access, SageMaker connects artifacts that reference the same object or data. If the data from one account is used in lineage tracking by different accounts, SageMaker creates an artifact in each account to track that data. With cross-account lineage, whenever SageMaker creates new artifacts, SageMaker checks if there are other artifacts created for the same data that are also shared with you. SageMaker then establishes associations between the newly created artifact and each of the artifacts shared with you with the AssociationType set to SameAs. You can then use the QueryLineage API action to traverse the lineage entities in your own account to lineage entities shared with you but owned by a different AWS account. For more information, see Querying Lineage Entities
Amazon SageMaker must validate that you have permissions to perform the QueryLineage API action on the StartArns. This is enforced through the resource policy attached to the LineageGroup. The result from this action includes all the lineage entities to which you have access, whether they are owned by your account or shared by another account. For more information, see Querying Lineage Entities.
df19127ead