- Knowledge Base
- Installation and System Setup
- Configuration
-
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 & Relationship
Key | Value | Description |
Lineage.shallow |
True/False |
When we send a query for lineage building, we verify whether that query is procedure / function / normal query. If it is not a normal query, we prefer shallow lineage to pick references from it. We make this TRUE, when lineage is not yet all build. |
Lineage.pick.anytable |
True/False |
While building the lineage, pick any table from queries which is available in oetable data. |
Ovaledge.namebasedrelationsjob.ispkbased |
True/False |
This param confirms whether to consider PK or not while building column name based relationships [client Specific UWM]. |
Lineage.debugmode |
True/False |
For get the temp tables -debug the temptable lineage |
Lineage.height.nodes |
Numbers
|
To show lineage graph width at max level |
Lineage.level.size |
Numbers |
Setting will show the specific levels in UI on both source and destination w.r.t.to selected object. |
Lineage.selfbuild |
True/False |
Setting for building self lineage from any Queries. |
shallow.lineage.connection.ids |
Connection id’s |
Add all possible connection ids to search tables / columns for shallow lineage |
lineage.width.nodes |
3 |
To show lineage graph width at max |
connections.order.lineage |
Empty |
Add needed connection id to pick the tables if multiple connections exists. |