> 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/references/engine-guide/trino-1/capabilities-and-limitations.md).

# Capabilities and limitations

Confirm Trino catalog compatibility, model support, and view security before deployment.

Use this page to confirm that your Trino catalogs and models work with Vulcan.

### Views and catalogs

Views are supported only when the catalog supports them. Iceberg catalogs must use an `iceberg.catalog.type` that supports views:

* `hive_metastore`
* `glue`
* `rest`

The `jdbc` and native `nessie` catalog types do not support views. They are incompatible with Vulcan. Vulcan's virtual layer is built from views.

DataOS lakehouse depots generate an Iceberg connector using REST and OAuth2. Views work on the standard depot path. Use Nessie only through REST, never through the native catalog type.

Hive-backed catalogs require these settings:

```properties
hive.allow-drop-table=true
hive.allow-add-column=true
hive.allow-drop-column=true
hive.allow-rename-table=true
hive.allow-rename-column=true
hive.metastore-cache-ttl=0s
```

### View limitations and security

Trino supports standard views with specific limitations around materialization, security, and execution context.

#### Materialized views

Materialized views are not supported.

#### Secure views

Secure views are not supported. `virtual_properties (creatable_type = SECURE)` is a Snowflake-only feature.

Vulcan passes `SECURE` through unchanged. The Trino coordinator then receives `CREATE SECURE VIEW` and returns a syntax error.

{% hint style="info" %}
Vulcan does not validate this setting for Trino. The error appears during apply, not during plan.
{% endhint %}

#### View execution and access control

A model definition cannot select Trino's `SECURITY DEFINER` or `SECURITY INVOKER` option.

Vulcan-created Trino views run with definer semantics. They read with the Vulcan service principal's privileges, not the querying user's privileges.

Do not use a Trino view as an access-control boundary. Enforce access through Trino access control, DataOS policies, and depot `purpose: query` credentials.

### Model and catalog limitations

Python models are not supported on Trino.

`INCREMENTAL_BY_PARTITION` is not supported on Postgres catalogs. Use `FULL` or `VIEW` instead.

Databricks catalogs are read-only. They use Iceberg REST against Unity Catalog. Writing to Databricks is not supported in this release.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://v2.dataos.info/references/engine-guide/trino-1/capabilities-and-limitations.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
