---
description: Feature supports in Trino
---

# Trino

## Feature Supports

<table data-view="cards"><thead><tr><th data-type="checkbox"></th><th></th><th data-hidden></th><th data-hidden></th></tr></thead><tbody><tr><td>true</td><td>Metadata </td><td></td><td></td></tr><tr><td>true</td><td>Query Usage</td><td></td><td></td></tr><tr><td>true</td><td>Data Profile</td><td></td><td></td></tr><tr><td>true</td><td>Lineage</td><td></td><td></td></tr><tr><td>true</td><td>DBT</td><td></td><td></td></tr><tr><td>false</td><td>Supported Versions</td><td></td><td></td></tr></tbody></table>

## Requirements

To run the Ingestion via the UI you'll need to use the metadata Ingestion Container, which comes shipped with custom Airflow plugins to handle the workflow deployment.

{% hint style="info" %}
To ingest metadata from the Trino source, the user must have select privileges for the following tables.

* `nformation_schema.schemata`
* `information_schema.columns`
* `information_schema.tables`
* `information_schema.views`
* `system.metadata.table_comments`
{% endhint %}

## Metadata Ingestion

### Step 1: Visit the Service Page

The first step is ingesting the metadata from your sources. Under Settings, you will find a Services link an external source system to Darkseal. Once a service is created, it can be used to configure metadata, usage, and profiler workflows.

To visit the Services page, select Services from the Settings menu or my-data table.

<figure><img src="https://3563943405-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FVh8UqeZpyXjjZSqpvE3I%2Fuploads%2FtFzViR3YkvmTmEec5UXo%2FScreen%20Shot%202023-03-19%20at%2017.08.25.png?alt=media&#x26;token=128c0aa8-4c6b-4c65-a6dc-33a93fbb38f8" alt=""><figcaption></figcaption></figure>

### Step 2: Create a New Service

Click on the Add New Service button to start the Service creation.

<figure><img src="https://3563943405-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FVh8UqeZpyXjjZSqpvE3I%2Fuploads%2F93A9FdE3fe9kTlHFsj3Y%2FScreen%20Shot%202023-03-19%20at%2017.09.17.png?alt=media&#x26;token=7f87fb91-9f53-474d-a0b1-1bd118178a49" alt=""><figcaption></figcaption></figure>

### Step 3: Select the Service Type

Select Trino as the service type and click Next.

<figure><img src="https://3563943405-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FVh8UqeZpyXjjZSqpvE3I%2Fuploads%2FFgiXydx2dNi98VXPwe9l%2FScreen%20Shot%202023-03-19%20at%2017.41.12.png?alt=media&#x26;token=d878267f-6951-4564-a79b-79dcfbcd2d3e" alt=""><figcaption></figcaption></figure>

### Step 4: Name and Describe your Service

Provide a name and description for your service as illustrated below.

<figure><img src="https://3563943405-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FVh8UqeZpyXjjZSqpvE3I%2Fuploads%2Fi4QBWbCrkyPc9isbm1jK%2FScreen%20Shot%202023-03-19%20at%2017.14.23.png?alt=media&#x26;token=0299ef19-10dc-4899-9754-879abb2bb025" alt=""><figcaption></figcaption></figure>

### Step 5: Configure the Service Connection

In this step, we will configure the connection settings required for this connector. Please follow the instructions below to ensure that you've configured the connector to read from your `Trino` service as desired.

<figure><img src="https://3563943405-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FVh8UqeZpyXjjZSqpvE3I%2Fuploads%2Fgk2L6k0JEa0csJ5IzTOF%2FScreen%20Shot%202023-03-19%20at%2017.42.15.png?alt=media&#x26;token=8a65cd25-6797-43c7-9cd8-b10ffb66312b" alt=""><figcaption></figcaption></figure>

Once the credentials have been added, click on `Test Connection` and Save the changes.

Connection options:

* **Username**: Specify the User to connect to Trino. It should have enough privileges to read all the metadata.
* **Password**: Password to connect to Trino.
* **Host and Port**: Enter the fully qualified hostname and port number for your Trino deployment in the Host and Port field.
* **Catalog**: Trino offers a catalog feature where all the databases are stored. (Providing the Catalog is not mandatory from 0.12.2 or greater versions)
* **DatabaseSchema**: DatabaseSchema of the data source. This is optional parameter, if you would like to restrict the metadata reading to a single databaseSchema. When left blank, OpenMetadata Ingestion attempts to scan all the databaseSchema.
* **Connection Options (Optional)**: Enter the details for any additional connection options that can be sent to Trino during the connection. These details must be added as Key-Value pairs.
* **Connection Arguments (Optional)**: Enter the details for any additional connection arguments such as security or protocol configs that can be sent to Trino during the connection. These details must be added as Key-Value pairs.
  * In case you are using Single-Sign-On (SSO) for authentication, add the `authenticator` details in the Connection Arguments as a Key-Value pair as follows: `"authenticator" : "sso_login_url"`
  * In case you authenticate with SSO using an external browser popup, then add the `authenticator` details in the Connection Arguments as a Key-Value pair as follows: `"authenticator" : "externalbrowser"`

### Step 6: Configure Metadata Ingestion

In this step we will configure the metadata ingestion pipeline, Please follow the instructions below:

Metadata Ingestion Options:

* **Name**: This field refers to the name of ingestion pipeline, you can customize the name or use the generated name.
* **Database Filter Pattern (Optional)**: Use to database filter patterns to control whether or not to include database as part of metadata ingestion.
  * **Include**: Explicitly include databases by adding a list of comma-separated regular expressions to the Include field. OpenMetadata will include all databases with names matching one or more of the supplied regular expressions. All other databases will be excluded.
  * **Exclude**: Explicitly exclude databases by adding a list of comma-separated regular expressions to the Exclude field. OpenMetadata will exclude all databases with names matching one or more of the supplied regular expressions. All other databases will be included.
* **Schema Filter Pattern (Optional)**: Use to schema filter patterns to control whether or not to include schemas as part of metadata ingestion.
  * **Include**: Explicitly include schemas by adding a list of comma-separated regular expressions to the Include field. OpenMetadata will include all schemas with names matching one or more of the supplied regular expressions. All other schemas will be excluded.
  * **Exclude**: Explicitly exclude schemas by adding a list of comma-separated regular expressions to the Exclude field. OpenMetadata will exclude all schemas with names matching one or more of the supplied regular expressions. All other schemas will be included.
* **Table Filter Pattern (Optional)**: Use to table filter patterns to control whether or not to include tables as part of metadata ingestion.
  * **Include**: Explicitly include tables by adding a list of comma-separated regular expressions to the Include field. OpenMetadata will include all tables with names matching one or more of the supplied regular expressions. All other tables will be excluded.
  * **Exclude**: Explicitly exclude tables by adding a list of comma-separated regular expressions to the Exclude field. OpenMetadata will exclude all tables with names matching one or more of the supplied regular expressions. All other tables will be included.
* **Include views (toggle)**: Set the Include views toggle to control whether or not to include views as part of metadata ingestion.
* **Include tags (toggle)**: Set the Include tags toggle to control whether or not to include tags as part of metadata ingestion.
* **Enable Debug Log (toggle)**: Set the Enable Debug Log toggle to set the default log level to debug, these logs can be viewed later in Airflow.
* **Mark Deleted Tables (toggle)**: Set the Mark Deleted Tables toggle to flag tables as soft-deleted if they are not present anymore in the source system.
* **Mark Deleted Tables from Filter Only (toggle)**: Set the Mark Deleted Tables from Filter Only toggle to flag tables as soft-deleted if they are not present anymore within the filtered schema or database only. This flag is useful when you have more than one ingestion pipelines. For example if you have a schema
* **Auto Tag PII(toggle)**: Auto PII tagging checks for column name to mark PII Sensitive/NonSensitive tag

### Step 7: Schedule the Ingestion and Deploy

Scheduling can be set up at an hourly, daily, or weekly cadence. The timezone is in UTC. Select a Start Date to schedule for ingestion. It is optional to add an End Date.

Review your configuration settings. If they match what you intended, click Deploy to create the service and schedule metadata ingestion.

If something doesn't look right, click the Back button to return to the appropriate step and change the settings as needed.

After configuring the workflow, you can click on Deploy to create the pipeline.

