How to Integrate Your External Trino Cluster With VAST

New
  • Published on Apr 10, 2026
  • 1 minute(s) read
Prev Next

Intro

While VAST provides a pre-configured Docker image (trino-vast) to simplify deployment, our architecture is designed around a standard Trino Connector. This means you can integrate the VAST Data Catalog (and the underlying VAST Database) into your own Trino environment by simply adding our plugin.

How to Integrate Your External Trino Cluster

To connect your existing Trino cluster, you need to follow these steps:

1. Obtain the VAST Connector Plugin:

You can download the trino-vast plugin from VAST’s support portal or their public GitHub repository.

2. Install the Plugin:

Copy the VAST plugin files into the plugin/ directory on every node (coordinator and workers) of your existing Trino cluster.

Typically, this path is /usr/lib/trino/plugin/vast/ or similar, depending on how you installed Trino.

3. Configure the Catalog:

Create a catalog configuration file (e.g., /etc/catalog/vast.properties) on your coordinator.

The basic configuration looks like this:

Ini, TOML

connector.name=vast
# The VIP pool or management IP of your VAST cluster
endpoint=http://<VAST_ENDPOINT>:80
# VAST uses S3-style credentials for catalog access
access_key_id=<YOUR_ACCESS_KEY>
secret_access_key=<YOUR_SECRET_KEY>
# Optional tuning
num_of_splits=64

Version Interoperability

Trino moves fast, and the VAST connector is sensitive to the Trino version because of internal API changes. You must match the VAST connector version to your Trino cluster version.

  • Trino Cluster Compatibility:

    • For VAST Cluster Version 5.3+: Use Connector 462

    • For VAST Cluster Version 5.2: Use Connector 443

    • For VAST Cluster Version 5.1: Use Connector 429

Why VAST Offers a "Fork"?

The version VAST ships in our documentation isn't a "fork" in the sense of a permanent divergent branch; it is usually just a validated LTS version of Trino bundled with:

  • The VAST Connector is pre-installed.

    • Specific performance tuning (like zstandard compression and split optimizations) is pre-configured.

  • Catalog-specific views for the vast_catalog schema.

    • By using your own cluster, you'll just need to ensure your Java version matches Trino's requirements (e.g., Java 22 or 23 for newer Trino releases) and that your network allows the Trino workers to talk to the VAST CNode VIPs over HTTP/HTTPS.

Related articles