> For the complete documentation index, see [llms.txt](https://v2.dataos.info/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://v2.dataos.info/build/v1/productize/connect-engine/trino/external-trino.md).

# External Trino

Use this path when you bring your own Trino cluster: Starburst, self-hosted Trino, or any Trino-compatible endpoint running outside DataOS. Vulcan only connects to it; it doesn't provision or manage the cluster. For the DataOS-managed shared cluster, use [Minerva](/build/v1/productize/connect-engine/trino/minerva.md) instead. To ship a cluster with the product, use [Dedicated Trino](/build/v1/productize/connect-engine/trino/dedicated-trino.md).

## Core settings

| Setting         | Value              |
| --------------- | ------------------ |
| Connection type | `trino`            |
| Dialect         | `trino`            |
| VDE             | `false` (required) |
| Scheduler       | Local or built-in  |

## Before you start

You need a running Trino endpoint and its host, port, user, catalog, and the authentication method it expects (for example, basic auth over HTTPS). Store the password in an environment variable locally, or a DataOS Secret when deploying.

## Permissions

The Trino user needs `CREATE SCHEMA` on the target catalog, `CREATE TABLE` and `CREATE VIEW` on schemas, `SELECT, INSERT, UPDATE, DELETE` on tables, and `DROP TABLE` for development and full rebuilds. Access control itself is connector/plugin-dependent (none, file-based, OPA, Ranger, or Starburst's own system). Check with whoever operates the cluster which model applies and how grants are expressed there.

## Connection options

Beyond `host`, `port`, `user`, `catalog`, and `password`, the adapter also accepts:

| Option                    | Description                                                                                                             |
| ------------------------- | ----------------------------------------------------------------------------------------------------------------------- |
| `method`                  | Auth method: `basic`, `ldap`, `jwt`, `kerberos`, `certificate`, `oauth`, or `no-auth`.                                  |
| `roles`                   | Catalog-to-role mapping for role-based access control.                                                                  |
| `http_headers`            | Extra HTTP headers sent with each request.                                                                              |
| `session_properties`      | Trino session properties.                                                                                               |
| `retries`                 | Number of request retries.                                                                                              |
| `timezone`                | Connection timezone.                                                                                                    |
| `schema_location_mapping` | Regex-to-location mapping for schema creation, for catalogs that can't infer table locations.                           |
| `catalog_type_overrides`  | Explicit connector type per catalog (for example `iceberg`, `hive`, `delta_lake`), when Vulcan can't reliably infer it. |

## config.yaml

```yaml
vde: false
gateways:
  default:
    connection:
      type: trino
      host: "<trino-host>"
      port: <port>
      user: "{{ env_var('TRINO_USER') }}"
      catalog: "<catalog>"
      http_scheme: https
      method: basic
      password: "{{ env_var('TRINO_PASSWORD') }}"
      verify: true
default_gateway: default
model_defaults:
  dialect: trino
  start: "2024-01-01"
```

If your endpoint authenticates differently, set `method` to whichever scheme it enables (`basic`, `ldap`, `jwt`, `kerberos`, `certificate`, `oauth`, or `no-auth`) plus the fields your provider documents. For Starburst and self-hosted specifics, see the [Trino engine manual](https://v2.dataos.info/references/engine-guide/trino-1/external-trino) in References.

## Supported model kinds

`VIEW`, `FULL`, `SEED`, `INCREMENTAL_BY_TIME_RANGE`, and `INCREMENTAL_BY_PARTITION`. For how each kind materializes, see the [Trino engine manual](https://v2.dataos.info/references/engine-guide/trino-1/external-trino).

Once the connection verifies, continue to [Assets](/build/v1/productize/assets.md).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://v2.dataos.info/build/v1/productize/connect-engine/trino/external-trino.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.