> 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.md).

# Trino

Trino is a distributed SQL query engine for analytics across data lakes, databases, and object storage. Use the `trino` adapter. The one decision to make here is who owns the cluster: that decides which path you follow.

| Path                                                                            | Use when                                                                                                       |
| ------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------- |
| [Dedicated Trino](/build/v1/productize/connect-engine/trino/dedicated-trino.md) | The cluster should be part of the Data Product deployment. Vulcan provisions and owns one cluster per product. |
| [Minerva](/build/v1/productize/connect-engine/trino/minerva.md)                 | You connect to DataOS Minerva, a shared, DataOS-managed Trino cluster in your tenant.                          |
| [External Trino](/build/v1/productize/connect-engine/trino/external-trino.md)   | You bring your own Trino-compatible endpoint, such as Starburst or self-hosted Trino.                          |

For the full Trino reference, including cluster tuning, failure modes, and local development, see the [Trino engine manual](https://v2.dataos.info/references/engine-guide/trino-1) in References.

## Rules for every Trino path

* `connection.type` is `trino`; `model_defaults.dialect` is `trino`.
* `vde: false`. Trino doesn't support `vde: true`.
* Store passwords and tokens in environment variables locally, and in DataOS Secrets when deploying.
* Use lowercase identifiers. Trino lowercases unquoted names; quote with `"` only for reserved words.

Pick the path that matches cluster ownership. If the cluster already exists and Vulcan only needs to connect, use [Minerva](/build/v1/productize/connect-engine/trino/minerva.md) for a shared, DataOS-managed cluster, or [External Trino](/build/v1/productize/connect-engine/trino/external-trino.md) for your own. If the cluster should ship with the product, use [Dedicated Trino](/build/v1/productize/connect-engine/trino/dedicated-trino.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.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.