-
Roadmap
-
Knowledgebase Documents
-
Installation and System Setup
-
Setup Data Catalog
-
Connectors
-
Data Discovery
-
Self Service
-
Access Management
-
Data Quality
-
Data Literacy
-
Privacy Compliance
-
Reporting
-
Architecture, Security & Releases
-
Developer's Zone
-
Advanced Tools
-
Record of Processing Activities (ROPA)
-
Others
-
Release6.0 User Guide
-
Release6.1 Features
-
Data Catalog
-
News
-
Deactivated_Old
-
Release6.3 Deep Dive Articles
Lineage related Configuration settings
Configuration Parameter | Options | Description |
lineage.selfbuild |
true / false |
Support lineage of an object to itself, to be shown in UI. Will create a destination table, suffixed with the count of the duplicate table number. |
lineage.pick.anytable |
true / false |
While resolving a data object, the default mode is to resolve within the context of the connection and schema. To ignore the context, select true. |
lineage.shallow |
true / false |
Shallow lineage limits the scope of lineage building to a specified list of connections. Set whether shallow lineage is enabled on not. |
Shallow.lineage.connection.ids: |
Connection Ids (comma separated) |
Add the connections that are part of the scope shallow lineage. |
lineage.debugmode: |
true / false |
Log temp lineage tables being created. Enable for debugging use. |
Connections.order.lineage |
Connection Ids (comma separated) |
Specify the connections that will be searched for a lineage data object. The order of search will be the order in which connections are specified. This is needed when data objects with same names are present in multiple connections. |
add.dataset.lineage.version |
true / false |
Enable lineage version support. |
need.hard.coded.values.in.lineage |
true / false |
Enable to include fixed values / data / hardcoded values within dataset queries as part of the lineage. |