Install the connector
The connector is a Trino plugin, installed into an existing Trino deployment. Deploy Trino first following the Trino deployment documentation.
For Kubernetes, see Connectors on Kubernetes, which covers the image and init container approaches.
Requirements
Trino server 435 through 478. An unsupported version can be forced with
gravitino.trino.skip-version-validation, but it is untested.
Every Trino node needs network access to the Gravitino server and to the underlying catalog
systems. The connector delegates to Trino's own connectors, so the ones for the catalog types you use must be
installed in Trino: hive, iceberg, mysql, postgresql, oracle, or sqlserver.
The coordinator must run with catalog.management=dynamic, which is not the default.
Choose the package
The connector is published to Maven Central as one zip per Trino version range, and the zip has to match the server. Each zip holds the complete plugin: the connector, its dependencies, and the Datastrato Enterprise additions such as Oracle and SQL Server support.
| Trino server | Artifact (com.datastrato, version 1.3.0) |
|---|---|
| 435 to 439 | datastrato-trino-connector-ext-435-439 |
| 440 to 445 | datastrato-trino-connector-ext-440-445 |
| 446 to 451 | datastrato-trino-connector-ext-446-451 |
| 452 to 468 | datastrato-trino-connector-ext-452-468 |
| 469 to 472 | datastrato-trino-connector-ext-469-472 |
| 473 to 478 | datastrato-trino-connector-ext-473-478 |
curl -sSfLO https://repo1.maven.org/maven2/com/datastrato/datastrato-trino-connector-ext-469-472/1.3.0/datastrato-trino-connector-ext-469-472-1.3.0.zip
Install
Unzip the archive and move the directory it contains into Trino's plugin directory. Trino loads
every directory under its plugin path, so the name is yours to choose; the examples use gravitino.
The plugin path differs between Trino images and distributions.
unzip -q datastrato-trino-connector-ext-469-472-1.3.0.zip
mv datastrato-trino-connector-ext-469-472-1.3.0 /usr/lib/trino/plugin/gravitino
Enable dynamic catalog management in etc/config.properties on the coordinator.
catalog.management=dynamic
Create etc/catalog/gravitino.properties with at least connector.name, gravitino.uri, and
gravitino.metalake. The full property set is on the
Trino connector page.
Restart Trino, then confirm with SHOW CATALOGS. The gravitino catalog means the plugin loaded.
Catalogs from your metalake appearing beside it means the server connection works. A gravitino
catalog alone usually means dynamic catalog management is off, the metalake name is wrong, or the
server is unreachable from the Trino nodes.
Connector logging is optional and enabled with a JVM argument.
-Dlog4j.configurationFile=file:///etc/trino/log4j2.properties