About the Denodo collector
Use this collector to harvest metadata for Denodo tables and columns across the enterprise systems and make it searchable and discoverable in data.world.
Important
The Denodo collector can be run in the Cloud or on-premise using Docker or Jar files.
Note
The latest version of the Collector is 2.247. To view the release notes for this version and all previous versions, please go here.
What is cataloged
The collector catalogs the following information.
Object | Information cataloged |
|---|---|
Database | Identifier, Type, Connection: name, Connection: port, Connection: server |
Name, Description, Primary keys, Foreign keys | |
Name, Description, Definition SQL | |
Name, Description, Definition VQL | |
Name, Description, Definition VQL | |
Columns | Name, JDBC type, Type, Type Name, Is Nullable, Default value, Key type (Primary, Foreign), Size, Index |
Stored Procedure | Name, Description, Return type |
Schema | Name (equivalent to database name) |
Relationships between objects
By default, the harvested metadata includes catalog pages for the following resource types. Each catalog page has a relationship to the other related resource types. If the metadata presentation for this data source has been customized with the help of the data.world Solutions team, you may see other resource pages and relationships.
Resource page | Relationship |
|---|---|
Base View | Contains Columns. Is part of Database |
Interface View | Contains Columns. Is part of Database |
Derived View | Contains Columns. Is part of Database |
Materialized Table | Contains Columns. Is part of Database |
Columns | Column is part of Base View, Interface View, Derived View or Materialized Table |
Database | Schema, Tables, Views, Stored Procedures contained in Database |
Schema | Schema has stored procedure |
Lineage for Denodo
Important things to note:
No lineage is available for materialized tables because Denodo does not provide the view SQL, nor do the Denodo stored procedures offer column dependency information.
The collector queries Denodo’s built-in VIEW_DEPENDENCIES(), GET_SOURCE_COLUMNS(), and COLUMN_DEPENDENCIES() stored procedures and DESC VQL WRAPPER JDBC, DESC VQL VIEW, and DESC VQL VIEW queries to find the tables and views from which each view selects data. It harvests a lineage relationship between the view and each of these dependent tables.
Table 3.Object
Lineage available
Column in Base View
The collector identifies the associated column in an upstream view or table from the JDBC source:
Where the data was derived from
Column in Derived View
The collector identifies the associated column in an upstream view or table:
Where the data is sourced from
That sort the rows via ORDER BY
That filter the rows via WHERE/HAVING
That aggregate the rows via GROUP BY
Note: For Derived Views, the collector first tries to parse the view SQL to harvest lineage metadata. If the collector parser cannot parse the derived view SQL, it uses Denodo stored procedures to gather column-level dependencies.
When harvesting metadata from Denodo stored procedures, the column-level dependencies only include relationships for columns selected from an upstream view or table. The collector will not identify columns involved in sorting the rows (ORDER BY), filtering the rows (WHERE/HAVING), or aggregating the rows (GROUP BY).
Column in Interface View
The collector identifies the associated column in an upstream view or table:
Where the column selects data from
Supported cross-system lineage
The currently supported data sources for cross-system lineage are:
Snowflake
SQL Server
PostgreSQL
Important
While other data sources are not formally supported, running the collector for those sources may still enable you to view cross-system lineage between Denodo and these sources.
Denodo versions supported
The collector supports Virtual DataPort version 8.0
Authentication supported
The collector supports username/password authentication to Denodo.