Connection to Impala

To connect an Apache Impala cluster to the DQC Platform, you provide the host and port of its HTTPS endpoint — typically an Apache Knox gateway — the database, the HTTP path of the Impala service, and the credentials of an LDAP user with read access. Every table in the database then becomes available for data quality checks.

Add an Impala connector

To begin:

Go to the Connectors > Data sources screen
Click the Impala tile
Enter the connection parameters described below

Required connection information

Field	Example	Description
Name	`Sales Impala`	A custom name to identify this connector inside DQC
User	`dqc_reader`	LDAP user with read permissions on the target database
Password	`{your password here}`	Password of the LDAP user
Host	`impala.example.com`	Hostname of the Impala endpoint — usually the Knox gateway. Bound to the connector and cannot be changed after creation.
Port	`8443`	Port of the HTTPS endpoint; `8443` for a standard Knox gateway. Bound to the connector.
Database	`default`	Name of the database to connect to. Defaults to `default`. Bound to the connector and cannot be changed after creation.
HTTP path	`gateway/<topology>/impala`	Path of the Impala service behind the gateway, where `<topology>` is your Knox topology name. Bound to the connector.

Authentication and transport

Authentication is LDAP — user and password are both required.
The connection always runs over HTTP transport with TLS. This is not optional: a connection without TLS is rejected when the connector is saved.
The server certificate is verified, so the endpoint needs a certificate DQC trusts.
Access through Apache Knox is the expected setup — point Host and Port at the gateway and name the Impala service in HTTP path.

Permissions and network

Create a dedicated read-only LDAP user (for example dqc_reader) with SELECT permission on exactly the databases and tables that should be quality-checked
DQC validates the connection by listing tables — the user has to be able to see them
If the cluster enforces IP allow-listing, whitelist the DQC platform's outbound IP

If the cluster is not reachable from the internet, connect it through the DQC Proxy.

What gets imported

Every table the user can read in the configured database becomes a DQC table
DQC only reads: every query it runs against Impala is read-only, and nothing is written back to the cluster
Host, port, database and HTTP path are bound to the connector and cannot be changed afterwards — create a new connector to point at a different cluster or database

Connect and assign permissions

After saving, DQC validates the credentials, lists the available tables and lets you pick which ones to expose. To control who can use the connector inside DQC, see Data source access permissions.