OpenMetadata/openmetadata-docs/content/v1.2.x-SNAPSHOT/connectors/database/trino/index.md

title	slug
Trino	/connectors/database/trino

Trino

{% multiTablesWrapper %}

Feature	Status
Stage	PROD
Metadata	{% icon iconName="check" /%}
Query Usage	{% icon iconName="cross" /%}
Data Profiler	{% icon iconName="check" /%}
Data Quality	{% icon iconName="check" /%}
Lineage	Partially via Views
DBT	{% icon iconName="check" /%}
Supported Versions	--

Feature	Status
Lineage	Partially via Views
Table-level	{% icon iconName="check" /%}
Column-level	{% icon iconName="check" /%}

{% /multiTablesWrapper %}

In this section, we provide guides and references to use the Trino connector.

Configure and schedule Trino metadata and profiler workflows from the OpenMetadata UI:

• Requirements
• Metadata Ingestion
• Data Profiler
• Data Quality
• dbt Integration

{% partial file="/v1.2/connectors/ingestion-modes-tiles.md" variables={yamlPath: "/connectors/database/trino/yaml"} /%}

Requirements

Metadata

To extract metadata, the user needs to be able to have SELECT permission to the following tables:

• information_schema.schemata
• information_schema.columns
• information_schema.tables
• information_schema.views
• system.metadata.table_comments

Access to resources will be based on the user access permission to access specific data sources. More information regarding access and security can be found in the Trino documentation here.

Profiler & Data Quality

Executing the profiler workflow or data quality tests, will require the user to have SELECT permission on the tables/schemas where the profiler/tests will be executed. More information on the profiler workflow setup can be found here and data quality tests here.

Metadata Ingestion

{% partial file="/v1.2/connectors/metadata-ingestion-ui.md" variables={ connector: "Trino", selectServicePath: "/images/v1.2/connectors/trino/select-service.png", addNewServicePath: "/images/v1.2/connectors/trino/add-new-service.png", serviceConnectionPath: "/images/v1.2/connectors/trino/service-connection.png", } /%}

{% stepsContainer %} {% extraContent parentTagName="stepsContainer" %}

Connection Details

• 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.
• proxies: Proxies for the connection to Trino data source
• params: URL parameters for connection to the Trino data source
• 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"

SSL Configuration

In order to integrate SSL in the Metadata Ingestion Config, the user will have to add the SSL config under connectionArguments which is placed in source.

SSL Modes There are a couple of types of SSL modes that redshift supports which can be added to ConnectionArguments, they are as follows:

• false: In order to disable SSL verification, set the verify parameter to False.
• <path-to-crt>: To use self-signed certificates, specify a path to the certificate in verify parameter. Find more details in the Python requests library documentation.

{% partial file="/v1.2/connectors/database/advanced-configuration.md" /%}

{% /extraContent %}

{% partial file="/v1.2/connectors/test-connection.md" /%}

{% partial file="/v1.2/connectors/database/configure-ingestion.md" /%}

{% partial file="/v1.2/connectors/ingestion-schedule-and-deploy.md" /%}

{% /stepsContainer %}

{% partial file="/v1.2/connectors/troubleshooting.md" /%}

{% partial file="/v1.2/connectors/database/related.md" /%}