Skip to content

You are viewing documentation for Immuta version 2022.4.

For the latest version, view our documentation for Immuta SaaS or the latest self-hosted version.

Starburst (Trino) Integration v2.0 Pre-Configuration Details

This page describes the Starburst (Trino) integration v2.0 configuration options and features.

See the Starburst (Trino) integration v2.0 page to enable the integration.

Feature Availability

Project Workspaces Tag Ingestion User Impersonation Native Query Audit Multiple Integrations
❌ ❌ ✅ ✅ ⚠


A valid Starburst (Trino) Enterprise license

Authentication Method

The Starburst (Trino) integration v2.0 supports authenticating with your Starburst (Trino) username and password to create data sources in Immuta.

Tag Ingestion

The Starburst (Trino) integration cannot ingest tags from Starburst (Trino), but you can connect any of these supported external catalogs to work with your integration.

User Impersonation

Impersonation allows users to query data as another Immuta user. To enable user impersonation, see the Integration User Impersonation page.

Native Query Audit

The Immuta Trino Event Listener allows Immuta to translate events into comprehensive audit logs for users with the Immuta AUDIT permission to view. For more information about what is included in those audit logs, see the Starburst (Trino) Audit Logs page.

In addition to the information included on the Starburst (Trino) Audit Logs page, the audit logs payload in the Starburst (Trino) integration v2.0 includes immutaPlanningDuration, which represents the planning overhead in Immuta.

Multiple Starburst (Trino) Instances

You can configure multiple Starburst (Trino) integrations v2.0 with a single Immuta instance and use them dynamically. However, names of catalogs cannot overlap because Immuta cannot distinguish among them. Only configure the integration once in Immuta to use it in multiple Starburst (Trino) instances.

Starburst (Trino)-Created Logical View Support

Immuta policies can be applied to Starburst (Trino)-created logical views.

The descriptions below provide guidance for applying policies to Starburst (Trino)-created logical views in the

However, there are other approaches you can use to apply policies to Starburst (Trino)-created logical views. The examples below are the simplest approaches.

Views Created in the DEFINER Security Mode

For views created using the DEFINER security mode,

  • ensure the user who created the view is configured as an admin user in the Immuta plugin so that policies are never applied to the underlying tables.
  • create Immuta data sources and apply policies to logical views exposing those tables.
  • lock down access to the underlying tables in Starburst (Trino) so that all end user access is provided through the views.

Views Created in the INVOKER Security Mode

Applying Policies to Views or Tables

Avoid creating data policies for both a logical view and its underlying tables. Instead, apply policies to the logical view or the underlying tables.

For views created using the INVOKER security mode, the querying user needs access to the logical view and underlying tables.

  • If non-Immuta table reads are disabled, provide access to the views and tables through Immuta. To do so, create Immuta data sources for the view and underlying tables, and grant access to the querying user in Immuta. If creating data policies, apply the policies to either the view or underlying tables, not both.

  • If non-Immuta table reads are enabled, the user already has access to the table and view. Create Immuta data sources and apply policies to the underlying table; this approach will enforce access controls for both the table and view in Starburst (Trino).

Policy Caveat

Limit your masked joins to columns with matching column types. Starburst truncates the result of the masking expression to conform to the native column type when performing the join, so joining two masked columns with different data types produces invalid results when one of the columns' lengths is less than the length of the masked value.

For example, if the value of a hashed column is 64 characters, joining a hashed varchar(50) and a hashed varchar(255) column will not be joined correctly, since the varchar(50) value is truncated and doesn’t match the varchar(255) value.