Connecting to Denodo
This section contains details for Denodo connections.
General information
Field | Description |
---|---|
Data source | Denodo |
Supported versions | 8.0-update-20240926 |
Connection string | jdbc:vdb://
|
Packaged? |
|
Certified? |
|
Supported features | |
Estimate job
|
|
Analyze data
|
|
Schedule
|
|
Processing capabilities | |
Pushdown
|
|
Spark agent
|
|
Yarn agent
|
|
Parallel JDBC
|
|
Java Platform version compatibility | |
JDK 8
|
|
JDK 11
|
|
Minimum user permissions
In order to bring your Denodo data into Collibra Data Quality & Observability, you need the following permissions.
- Read access on Denodo tables.
- ROLE_ADMIN assigned to your user in Collibra DQ.
Recommended and required connection properties
Required | Connection Property | Type | Value |
---|---|---|---|
|
Name | Text | The unique name of your connection. Ensure that there are no spaces in your connection name. |
|
Connection URL | String |
The connection string path of your Denodo connection. When referring to the example below, replace the Example |
|
Driver Name | String |
The driver class name of your Denodo connection.
|
|
Port | Integer |
The port number to establish a connection to the datasource. The default port is |
|
Limit Schemas | Option |
Allows you to manage usage and restrict visibility to only the necessary schemas in the Explorer tree. See Limiting schemas to learn how to limit schemas from the Connection Management page. Note When you include a restricted schema in the query of a DQ Job, the query scope may be overwritten when the job runs. While only the schemas you selected when you set up the connection are shown in the Explorer menu, users are not restricted from running SQL queries on any schema from the data source. |
|
Source Name | String | N/A |
|
Target Agent | Option | The Agent that submits your Spark job for processing. |
|
Auth Type | Option |
The method to authenticate your connection. Note The configuration requirements are different depending on the Auth Type you select. See Authentication for more details on available authentication types. |
|
Driver Properties | String |
The configurable driver properties for your connection. Multiple properties must be comma delimited. For example, abc=123,test=true When you use the OAuth2 authentication method, add the following semicolon-separated ; properties, adjusting the parameterized section (
Example
|
Authentication
Select an authentication type from the dropdown menu. The options available in the dropdown menu are the currently supported authentication types for this data source.
Important
When you use OAuth2 authentication, you need to add the following IdP parameters to the Driver Properties input field on the Properties tab:dq.idp.url=${ }
dq.idp.scopes=${ }
dq.idp.grantType=${ }
See the Driver Properties section above for more information.
Required | Field | Description |
---|---|---|
|
Username | The username of your Denodo account. |
|
Password | The password of your Denodo account. |
|
Username | The username credential required for the IdP service to authenticate a user. |
|
Password | The password credential required for the IdP service to authenticate a user. |
|
Script |
The file path that contains the script file that the password manager uses to interact with and authenticate a user account. Example /tmp/keytab/denodo_pwd_mgr.sh |
|
Param $1 | Optional. An additional parameters to authenticate your Denodo connection. |
|
Param $2 | Optional. An additional parameter to authenticate your Denodo connection. |
|
Param $3 | Optional. An additional parameter to authenticate your Denodo connection. |
Known limitations
- Denodo connections do not support queries with a LIMIT filter, because the Denodo's proprietary query language (VQL) does not support the LIMIT operator.