> For the complete documentation index, see [llms.txt](https://docs.collibra.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.collibra.com/data-quality-self-hosted/connections/supported-connections/supported-jdbc-data-sources/connecting-to-apache-impala.md). # Connecting to Apache Impala This section contains details for Impala connections. Select an option from the dropdown menu to display information for a particular driver class. {% tabs %} {% tab title="Native" %} ## General information
FieldDescription
Data sourceApache Impala
Supported versions2.6.28
Connection stringjdbc:impala://
Packaged? Yes
Certified? Yes
Supported features
Estimate job Yes
Analyze data Yes
Schedule Yes
Processing capabilities
Pushdown No
Spark agent Yes
Yarn agent Yes
Parallel JDBC Yes
Java Platform version compatibility
JDK 8 Yes
JDK 11 Yes
## Minimum user permissions In order to bring your Impala data into Data Quality & Observability (self-hosted), you need the following permissions. * The Kerberos user has read permissions on Impala tables. * ROLE\_ADMIN assigned to your user in Collibra DQ. ## Recommended and required connection properties | Required | Connection Property | Type | Value | | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------- | ------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Yes | Name | Text | The unique name of your connection. Ensure that there are no spaces in your connection name. | | No | Hive Direct Eligible | Option | Uses the Hive server engine for distributed speed and scale. | | Yes | Connection URL | String |

The connection string path of your Impala connection.

When referring to the example below, replace the ${value} sections of the connection URL with your actual value.

:glasses-round: Example: jdbc:impala://${host}:21050/default;AuthMech=1;KrbHostFQDN=${host};KrbServiceName=impala;SSL=1;AllowSelfSignedCerts=1

| | Yes | Driver Name | String |

The driver class name of your connection.

com.cloudera.impala.jdbc.Driver

| | Yes | Port | Integer |

The port number to establish a connection to the datasource.

The default port is 21050

| | No | 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.

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.

| | No | Source Name | String | N/A | | No | Target Agent | Option | The [Agent](/data-quality-self-hosted/installation/agent.md) that submits your Spark job for processing. | | Yes | Auth Type | Option |

The method to authenticate your connection.

The configuration requirements are different depending on the Auth Type you select. See Authentication for more details on available authentication types.

| | No | Driver Properties | String |

The configurable driver properties for your connection. Multiple properties must be semicolon-delimited, and each property=value pair, including the last one, must end with a semicolon (;). abc=123;test=true;

Optionally add the following driver property to remove the enforcement of unique column names:

hive.resultset.use.unique.column.names=false

| | {% endtab %} | | | | {% tab title="CDATA" %} ## General information
FieldDescription
Data sourceApache Impala
Supported versions21.0.8137.0
Connection stringjdbc:impala://
Packaged? Yes
Certified? Yes
Supported features
Estimate job No
Analyze data No
Schedule No
Processing capabilities
Pushdown No
Spark agent Yes
Yarn agent Yes
Parallel JDBC Yes
Java Platform version compatibility
JDK 8 Yes
JDK 11 Yes
## Minimum user permissions In order to bring your Impala data into Data Quality & Observability (self-hosted), you need the following permissions. * The Kerberos user has read permissions on Impala tables. * ROLE\_ADMIN assigned to your user in Collibra DQ. ## Recommended and required connection properties | Required | Connection Property | Type | Value | | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------- | ------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Yes | Name | Text | The unique name of your connection. Ensure that there are no spaces in your connection name. | | No | Hive Direct Eligible | Option | Uses the Hive server engine for distributed speed and scale. | | Yes | Connection URL | String |

The connection string path of your Impala connection.

When referring to the example below, replace the ${value} sections of the connection URL with your actual value.

:glasses-round: Example: jdbc:impala://${host}:21050/default;AuthMech=1;KrbHostFQDN=${host};KrbServiceName=impala;SSL=1;AllowSelfSignedCerts=1

| | Yes | Driver Name | String |

The driver class name of your connection.

cdata.jdbc.apacheimpala.ApacheImpalaDriver

| | Yes | Port | Integer |

The port number to establish a connection to the datasource.

The default port is 21050

| | No | 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.

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.

| | No | Source Name | String | N/A | | No | Target Agent | Option | The [Agent](/data-quality-self-hosted/installation/agent.md) that submits your Spark job for processing. | | Yes | Auth Type | Option |

The method to authenticate your connection.

The configuration requirements are different depending on the Auth Type you select. See Authentication for more details on available authentication types.

| | No | Driver Properties | String |

The configurable driver properties for your connection. Multiple properties must be semicolon-delimited, and each property=value pair, including the last one, must end with a semicolon (;). abc=123;test=true;

Optionally add the following driver property to remove the enforcement of unique column names:

hive.resultset.use.unique.column.names=false

| | {% endtab %} | | | | | {% endtabs %} | | | | ## 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. {% tabs %} {% tab title="Kerberos Password Manager" %} | Required | Field | Description | | ------------ | ----- | ----------- | | {% endtab %} | | | {% tab title="Kerberos Keytab" %}
RequiredFieldDescription
YesPrincipalThe Kerberos entity to authenticate and grant access to your connection.
YesKeytab

The file path of the keytab file that contains the encrypted key for a Kerberos principal.

:glasses-round: Example: /tmp/keytab/impala_user.keytab

{% endtab %} {% tab title="Kerberos Password" %}
RequiredFieldDescription
YesPrincipalThe Kerberos entity to authenticate and grant access to your connection.
YesPasswordThe secret credential associated with your Kerberos principal.
{% endtab %} {% tab title="Password TGT Cache" %}
RequiredFieldDescription
YesPrincipalThe Kerberos entity to authenticate and grant access to your connection.
YesTGT CacheThe ticket-granting ticket cache that stores the TGT to authenticate your connection.
{% endtab %} {% tab title="Access Token Manager" %} ### Configuring Access Token Manager authentication #### Prerequisites You have added a script file that contains or can retrieve an access token to a folder accessible to Data Quality & Observability (self-hosted). #### Steps {% stepper %} {% step %} Update the Connection URL to the following format: `jdbc:impala://${host}:${port}/${catalog}?SSL=true&source=jdbc:impala&accessToken=${accessToken}` {% endstep %} {% step %} Select **Access Token Manager** from the Authentication Type dropdown menu. {% endstep %} {% step %} Enter the User ID of the IdP account in the Username input field. {% endstep %} {% step %} Enter the file path containing the access token script file in the Script input field. For example, /opt/owl/config/get\_impala.sh {% endstep %} {% step %} Click Submit. {% endstep %} {% endstepper %}
RequiredFieldDescription
YesUsernameThe User ID of the IdP account.
YesScript

The file path containing the access token script file in the Script input field.

:glasses-round: Example: /opt/owl/config/get_impala.sh

NoParam $1Optional. Additional parameter.
NoParam $2Optional. Additional parameter.
NoParam $3Optional. Additional parameter.
{% endtab %} {% endtabs %}