Trino¶

Trino (formerly PrestoSQL) is a distributed SQL query engine designed for fast analytics on large datasets across multiple data sources.

omniload supports Trino as both a source and destination.

[!WARNING] Trino is currently supported as a beta platform, which means that some features might not work as expected.

URI format¶

The URI format for Trino is as follows:

trino://<username>:<password>@<host>:<port>/<catalog>

URI parameters:

username: your Trino username (required)
password: your Trino password (optional, depending on authentication)
host: the Trino server hostname or IP address
port: the Trino server port (default: 8080)
catalog: the Trino catalog to connect to

The same URI structure can be used both for sources and destinations. You can read more about SQLAlchemy’s Trino dialect here.

Authentication methods¶

Trino supports various authentication methods:

No Authentication: For development/testing environments
```
trino://user@localhost:8080/catalog
```

Basic Authentication: Username and password

trino://user:password@localhost:8080/catalog

Other Methods: For Kerberos, JWT, or certificate-based authentication, consult your Trino administrator for the appropriate connection parameters.

Table naming¶

When specifying tables for Trino (both source and destination), use the format:

schema.table_name

For example:

default.users - accesses the users table in the default schema
analytics.events - accesses the events table in the analytics schema

The catalog is specified in the connection URI, not in the table name.

Examples¶

Using Trino as a source¶

omniload ingest \
    --source-uri 'trino://admin@localhost:8080/iceberg' \
    --source-table 'default.source_table' \
    --dest-uri 'duckdb:///output.db' \
    --dest-table 'main.destination_table'

Using Trino as a destination¶

omniload ingest \
    --source-uri 'postgresql://user:pass@localhost:5432/sourcedb' \
    --source-table 'public.customers' \
    --dest-uri 'trino://admin@localhost:8080/hive' \
    --dest-table 'default.customers'

With authentication¶

omniload ingest \
    --source-uri 'mysql://user:pass@localhost:3306/sourcedb' \
    --source-table 'orders' \
    --dest-uri 'trino://user:password@trino-server:8443/iceberg' \
    --dest-table 'sales.orders'

Supported write dispositions¶

When using Trino as a destination, all the existing write dispositions are supported.

Data type handling¶

Trino automatically handles most SQL data type conversions. When used as a destination:

JSON types are converted to TEXT/VARCHAR
Binary types are converted to TEXT/VARCHAR
All integer types are mapped to BIGINT for compatibility

Limitations¶

As a destination¶

Case-sensitive identifiers (table and column names preserve case)
JSON and Binary types are converted to STRING
Memory catalog does not support DELETE and UPDATE operations (affects merge/scd2 in test environments)