Denodo OCF Connector: Overview¶
Alation Cloud Service Applies to Alation Cloud Service instances of Alation
Customer Managed Applies to customer-managed instances of Alation
Core Connector Core connectors are included with all Alation platform tiers (subject to each tier’s connector limits) and are fully supported by Alation.
You can install and upgrade the connector using one of the following methods, depending on your Alation deployment type:
On-premise instances: Download the latest connector package from the Alation Customer Portal (Customer Portal > Connectors), then upload and install it in Alation.
Alation Cloud Service: Install and upgrade the connector directly from your instance without downloading the package. Any connector available on the Alation Customer Portal (Customer Portal > Connectors) can be installed and upgraded this way. See Install Connectors (Cloud-Native Architecture). You can also download the connector package from the Alation Customer Portal and install or upgrade it manually by uploading the Zip file.
This connector should be used to catalog Denodo as a data source on Alation on-prem and Alation Cloud Service instances. It extracts and catalogs such database objects as schemas, tables, columns, primary key, and views fields. After the metadata is extracted, it is represented in the data catalog as a hierarchy of catalog pages under the parent data source. Alation users can leverage the full catalog functionality to search for and find the extracted metadata, curate the corresponding catalog pages, create documentation about the data source, and exchange information about it.
Team¶
The following administrators are required to install this connector:
Alation administrator:
Ensures that Alation Connector Manager is installed and running or installs it.
Installs the connector.
Creates and configures the Denodo data source in the catalog.
Performs initial extraction and prepares the data source for Alation users.
Denodo administrator:
Creates a service account.
Provides the JDBC URI to access metadata
Provides access to databases to extract metadata.
Scope¶
The table below shows which metadata objects are extracted by this connector and which operations are supported.
Feature |
Scope |
Availability |
|---|---|---|
Authentication |
||
Basic authentication |
Authentication with username and password |
Yes |
LDAP |
Authentication with the LDAP protocol |
No |
Kerberos |
Authentication with Kerberos |
No |
Keytab |
Authentication with Keytab |
No |
SSL |
SSL Authentication |
Yes |
SSO |
Authentication using an SSO flow through an IdP application |
No |
Metadata Extraction (MDE) |
||
Default MDE |
Extraction of metadata based on the JDBC driver methods in the connector code |
Yes |
Custom query-based MDE |
Extraction of metadata based on extraction queries provided by a user |
No |
Extracted metadata objects |
||
Data Source |
Data source object in Alation that is parent to the extracted metadata |
No |
Schemas |
List of schemas |
Yes |
Tables |
List of tables |
Yes |
Columns |
List of columns |
Yes |
Column comments |
column comments |
No |
Column data types |
Column data types |
No |
Views |
List of views |
Yes |
Source comments |
Source comments |
No |
Primary keys |
Primary key information for extracted tables |
Yes |
Foreign keys |
Foreign key information for extracted tables |
No |
Functions |
Extract function metadata |
No |
Function definitions |
Extract function definition metadata |
No |
Sampling and Profiling |
||
Table sampling |
Retrieval of data samples from extracted tables |
Yes |
Column sampling |
Retrieval of data samples from extracted columns |
Yes |
Deep column profiling |
On-demand profiling of specific columns with the calculation of value distribution stats |
Yes |
Dynamic profiling |
On-demand table and column profiling by individual users who use their own database accounts to retrieve the profiles |
Yes |
Custom query-based table sampling |
Ability to use custom queries for sampling specific tables |
Yes |
Custom query-based column sampling |
Ability to use custom queries for profiling specific columns |
No |
Query Log Ingestion (QLI) |
||
Table-based QLI |
Ingestion of query history based on a table that contains query history data |
Yes |
File-based QLI |
Ingestion of query history based on a file that contains query history data |
No |
Query-based QLI |
Ingestion of query history based on a custom query history extraction query |
Yes |
JOINs and filters |
Calculation of JOIN and filter information based on ingested query history |
Yes |
Predicates |
Ability to parse predicates in ingested queries |
Yes |
Popularity |
Indicator of the popularity (intensity of use) of a data object, such as a table or a column |
Yes |
Lineage |
||
Automatic lineage generation |
Auto-calculation of lineage from ingested query history (QLI). Lineage for this connector is produced by direct lineage extraction during metadata extraction, not from QLI. |
No |
Direct lineage extraction |
Lineage information is calculated during metadata extraction. It covers view-to-view and column-to-column relationships within Denodo and does not require query log ingestion (QLI). |
Yes* |
Compose |
||
Customer-managed (on-prem) Alation instances |
Compose on on-prem Alation instances |
Yes |
Alation Cloud Service instances |
Compose via Agent is supported from connector version 1.2.0.4956. |
Yes |
Basic Authentication in Compose |
Authentication in Compose with username and password |
Yes |
Query creation and execution |
Yes |
|
OAuth in Compose |
Authentication in compose with OAuth Credentials |
No |
SSO authentication in Compose |
Authentication in compose with SSO Credentials |
No |
* Direct lineage extraction is supported from connector version 1.5.0.