Configure the Trino Delta Lake Connector on a Kerberized ODP Cluster

Trino can query Delta Lake tables only after a Delta Lake catalog is configured with access to the appropriate metastore and storage.

On Kerberized ODP clusters, additional Kerberos configuration for both the Hive Metastore and HDFS is required so Trino can authenticate to those services.

Symptoms

Queries against Delta Lake tables might fail with errors similar to:

Bash
Copy

or

Bash
Copy

Cause

The Delta Lake connector is available in Trino but is not configured by default.

Resolution

Create a Delta Lake catalog

Create a catalog file under:

Bash
Copy

The file should be a properties file (*.properties) bearing the desired name for your delta lake catalog.

For example, if you wish your catalog to be called “sales”. Then you should create a file called sales.properties at the location /etc/trino/conf/catalog/.

The fully qualified path of the file will be/etc/trino/conf/catalog/sales.properties

A minimal catalog properties file looks as follows:

Bash
Copy

Configure Kerberos authentication

For Kerberized clusters, add:

Bash
Copy

Configure Hadoop resources

Bash
Copy

Apply the configuration on all nodes

The catalog file must exist on:

  • Trino Coordinator
  • All Trino Worker nodes

Ensure the configured principal matches the keytab available on each node.

Validate the configuration

List available catalogs:

Bash
Copy

Query a Delta Lake table:

Bash
Copy

Result

With the Delta Lake catalog and Kerberos authentication configured, Trino can successfully authenticate with the Hive Metastore and HDFS, enabling it to query Delta Lake tables on a Kerberized ODP cluster.

VariableType to search · ESC to discard
GlossaryType to search · ESC to discard
InsertType to search · ESC to discard
No matches