Trino

Adding and configuring a Trino connection within Qualytics empowers the platform to build a symbolic link with your schema to perform operations like data discovery, visualization, reporting, syncing, profiling, scanning, anomaly surveillance, and more.

This documentation provides a step-by-step guide on adding Trino as a source datastore in Qualytics. It covers the entire process, from initial connection setup to testing and finalizing the configuration.

By following these instructions, enterprises can ensure their Trino environment is properly connected with Qualytics, unlocking the platform’s potential to help you proactively manage your full data quality lifecycle.

Let’s get started 🚀

Trino Setup Guide

Qualytics connects to Trino through the Trino JDBC driver. It uses standard SQL queries for data profiling and scanning. Since Trino is a distributed query engine, permissions are determined by the underlying data source (connector) configured in the Trino catalog (e.g., Hive, Delta Lake, Iceberg, RDBMS).

Minimum Trino Permissions (Source Datastore)

The actual permissions depend on the Trino security model configured for your deployment:

Example: File-Based Access Control Configuration

If your Trino deployment uses file-based access control (rules.json), ensure the Qualytics user has appropriate access to the target catalog and schema:

{
  "catalogs": [
    {
      "user": "qualytics_read",
      "catalog": "<catalog_name>",
      "allow": "read-only"
    }
  ]
}

Troubleshooting Common Errors

Detailed Troubleshooting Notes

Authentication Errors

The error Authentication failed indicates that the credentials are incorrect or the authentication method does not match the server configuration.

Common causes:

• Incorrect password: the password does not match the one configured in the Trino server.
• Wrong authentication method: the Trino server uses LDAP or Kerberos, but the connection form provides basic username/password.
• HTTPS required: the Trino coordinator requires HTTPS connections, but the connection is using HTTP.

Permission Errors

The error Access Denied: Cannot select from table or Access Denied: Cannot create table means the user authenticated successfully but lacks access to the target resource.

Common causes:

• File-based access control: the rules.json file does not grant the required permissions to the Qualytics user.
• Connector-level security: the underlying data source does not grant the necessary access.

Connection Errors

The error Connection refused or Catalog does not exist indicates a connectivity or configuration issue.

Common causes:

• Coordinator not reachable: the Trino coordinator host or port (default 8080) is incorrect.
• Wrong catalog name: the catalog name in the connection form does not match a configured Trino catalog.
• Coordinator not running: the Trino coordinator process is not started.

Add a Source Datastore

A source datastore is a storage location Qualytics connects to so it can profile, scan, and monitor data. Adding Trino as a source lets Qualytics query it through the Trino JDBC driver and run quality operations on the tables it discovers.

Before you start, review the Minimum Trino Permissions the connecting user needs.

Field reference

The Add Datastore page shows the sections below when Trino is selected. When reusing an existing connection, the Connection Properties and Secrets Management sections come already filled in and read-only: Qualytics has already validated those credentials, so you fill in only the Datastores Extraction and the Datastore Properties. To change a saved connection's credentials, edit the connection through the Manage Connections page; edits there apply to every datastore that reuses the connection.

Connection Properties

These fields define the Trino coordinator Qualytics connects to and the account it connects with. They belong to the connection: when reusing an existing connection, they come already filled in and read-only.

Secrets Management

This group is optional: use it only if you want Qualytics to pull credentials from a secrets manager instead of typing them into the form. Turn on HashiCorp Vault to show the fields below. Despite the label, any secrets manager that exposes a compatible REST API works, not only HashiCorp Vault; see Secrets Management. It also belongs to the connection: read-only when reusing an existing connection.

Datastores Extraction

Pick the catalog and the schema or schemas Qualytics should read from, and choose whether the connection is encrypted. You fill these in on both flows.

Datastore Properties

Common fields for every source datastore, shown below the Datastores Extraction section. You fill these in on both flows.

Steps

There are two ways to set up the connection: reuse a connection you already saved (Existing Connection) or create a new one from scratch (New Connection). The tabs below walk through each option; pick the one you want to follow. Each field is described in the Field reference above.

API Payload Examples

Creating a Datastore

This section provides a sample payload for creating a datastore. Replace the placeholder values with actual data relevant to your setup.

Endpoint (Post)

/api/datastores (post)

    {
        "name": "your_datastore_name",
        "teams": ["Public"],
        "database": "trino_database",
        "schema": "trino_schema",
        "enrichment_only": false,
        "trigger_sync": true,
        "connection": {
            "name": "your_connection_name",
            "type": "trino",
            "host": "trino_host",
            "port": 8080,
            "username": "trino_username",
            "password": "trino_password"
        }
    }

    {
        "name": "your_datastore_name",
        "teams": ["Public"],
        "database": "trino_database",
        "schema": "trino_schema",
        "enrichment_only": false,
        "trigger_sync": true,
        "connection_id": 123
    }

# Step 1: Create a Connection
qualytics connections create \
    --type trino \
    --name "your_connection_name" \
    --host ${TRINO_HOST} \
    --port 8080 \
    --username ${TRINO_USER} \
    --password ${TRINO_PASSWORD}

# Step 2: Create a Source Datastore
qualytics datastores create \
    --name "your_datastore_name" \
    --connection-name "your_connection_name" \
    --database your_catalog \
    --schema default

"connection": {
    "name": "your_connection_name",
    "type": "trino",
    "host": "trino_host",
    "port": 8080,
    "username": "trino_username",
    "password": "trino_password",
    "parameters": {
        "ssl": "false"
    }
}

Linking Datastore to an Enrichment Datastore through API

Endpoint (Patch)

/api/datastores/{datastore-id}/enrichment/{enrichment-id} (patch)