Trino Connector | OpenMetadata Distributed SQL Integration

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
• Lineage
• Data Profiler
• Data Quality
• dbt Integration
• Troubleshooting

​

Requirements

Before configuring the Trino connector, make sure the following requirements are in place.

​

Metadata

To extract metadata, the user needs to have SELECT privilege on all the tables that you would like to ingest in OpenMetadata, as well as SELECT privilege on the system.metadata.table_comments table. Access to resources is based on the user’s access permission to specific data sources. More information regarding access and security can be found in the Trino documentation.

​

Profiler & Data Quality

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

​

Metadata Ingestion

To ingest metadata from Trino, you need to create a service connection. The service connects Trino with OpenMetadata. Once you create a service, OpenMetadata automatically starts ingesting metadata.

​

Step 1: Add New Service

1. Navigate to Settings > Services.
2. Click Add New Service.

​

Step 2: Select a Service and Connector

From the service type dropdown, select Database Services, then click the Trino connector tile.

​

Step 3: Add Service Name and Description

• Enter a unique, descriptive Service Name. OpenMetadata identifies services by their service name. Enter a name that distinguishes this deployment from other Trino services you are ingesting metadata from.
• Optional: Enter a Description for the service.

​

Step 4: Configure Connection Options

Specify your source credentials and verify the connection.

​

Enter Connection Details

Enter the connection details for Trino. The right-hand panel in the UI displays inline help for each field. Connection

• Username: Specify the user to connect to Trino. It should have enough privileges to read all the metadata.
• 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.
• Database Schema: Database schema of the data source. This is an optional parameter, if you would like to restrict the metadata reading to a single database schema. When left blank, OpenMetadata attempts to scan all the database schemas.

Authentication Authenticate the Trino instance with Basic Authentication (password) or JWT Authentication:

• Basic Auth:
  • Password: Password to connect to Trino.
• JWT Auth Config:
  • JWT: JWT can be used to authenticate with Trino. Follow the steps in the official Trino documentation to set up Trino with JWT.
• Azure:
  • Client ID: To get the Client ID (also known as application ID), follow these steps:
    1. Log into Microsoft Azure.
    2. Search for App registrations and select the App registrations link.
    3. Select the Azure AD app you’re using for Trino.
    4. From the Overview section, copy the Application (client) ID.
  • Client Secret: To get the client secret, follow these steps:
    1. Log into Microsoft Azure.
    2. Search for App registrations and select the App registrations link.
    3. Select the Azure AD app you’re using for Trino.
    4. Under Manage, select Certificates & secrets.
    5. Under Client secrets, select New client secret.
    6. In the Add a client secret pop-up window, provide a description for your application secret. Choose when the application should expire, and select Add.
    7. From the Client secrets section, copy the string in the Value column of the newly created application secret.
  • Tenant ID: To get the tenant ID, follow these steps:
    1. Log into Microsoft Azure.
    2. Search for App registrations and select the App registrations link.
    3. Select the Azure AD app you’re using for Trino.
    4. From the Overview section, copy the Directory (tenant) ID.
  • Scopes: To let OpenMetadata use the Trino Auth APIs using your Azure AD app, add the scope:
    1. Log into Microsoft Azure.
    2. Search for App registrations and select the App registrations link.
    3. Select the Azure AD app you’re using for Trino.
    4. From the Expose an API section, copy the Application ID URI.
    5. Make sure the URI ends with /.default; if it does not, append it manually.

Advanced Config (driver-level options; most connections don’t need these)

• proxies: Proxies for the connection to the Trino data source.
• params: URL parameters for the 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.
  • If you are using Single Sign-On (SSO) for authentication, add the authenticator details in the Connection Arguments as a key-value pair, for example "authenticator" : "sso_login_url".

SSL Configuration To integrate SSL in the Metadata Ingestion config, add the SSL config under connectionArguments, which is placed in source. There are a couple of SSL modes supported, which can be added to connectionArguments:

• false: 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 the verify parameter.

Find more details in the Python requests library documentation.

​

Test Connection

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

​

Step 5: Configure Ingestion Options

In the What to Ingest step, use filter patterns to control which assets OpenMetadata ingests from your database service. Filter patterns use regular expressions applied to asset names.

​

How Filter Patterns Work

• Include: Add one or more comma-separated regular expressions. OpenMetadata ingests only assets whose names match at least one expression. Leave blank to include all assets.
• Exclude: Add one or more comma-separated regular expressions. OpenMetadata skips any asset whose name matches an expression. Leave blank to exclude nothing.

Rules match asset names using one of five expressions:

• contains: matches any name containing the value. For example, sales matches my_sales_data and sales_2024.
• starts with: matches names beginning with the value. For example, prod_ matches prod_db and prod_schema.
• ends with: matches names ending with the value. For example, _raw matches events_raw and logs_raw.
• is exactly: matches the exact name only. For example, analytics matches only analytics.
• matches regex: matches names using a regular expression. For example, ^prod_.*_v\d+$ matches prod_events_v1.

When both Include and Exclude are set, Exclude takes priority. Filter Options The Database, Schema, and Table sections each include the following filter options:

• Database: Controls which databases OpenMetadata ingests from the source.
• Schema: Controls which schemas within the ingested databases are included.
• Table: Controls which tables and views within the ingested schemas are included.

Each section provides the following controls:

• Scan Mode: You can choose between the following scan modes:
  • Scan all: Ingests every asset of that type the connector can access. This is the default.
  • Only specific: Enables include rules so only assets matching at least one rule are ingested.
• Exclude system toggle: Use this toggle to automatically filter out system-reserved names defined by the connector, for example, Exclude system databases for the Databases section.
• Always exclude: Add permanent exclusion rules (shown in red). Assets matching these rules are never ingested, regardless of include rules.
• Preview: Shows a real-time summary of what will be in scope based on your current rules.
• Include rules (available only in Only specific mode): Click + Add to define a rule. Added rules appear as chips; an asset is included if it matches any rule.

​

Step 6: Create & Deploy

Click Create & Deploy to deploy the agent and start the first metadata ingestion run. OpenMetadata saves the service configuration and immediately begins pulling metadata from the source. To monitor ingestion progress or view the service you just added, go to Settings > Services and select your service.

​

Configure Metadata Agent and Schedule Ingestion

The Metadata Agent extracts schemas, tables, columns, and other structural metadata from your source and keeps your OpenMetadata catalog in sync. It powers discovery, lineage, and governance across your data assets. When you click Create & Deploy, OpenMetadata automatically deploys a Metadata Agent for this service and triggers the first ingestion run. View its status and run history from the Agents tab on the service detail page. To configure the additional Metadata Agent and schedule ingestion, follow these steps:

1. Navigate to Settings > Services and select the service type.
2. Click the service you have added.
3. Select the Agents tab and click Add Agent > Metadata. For some services, the dropdown is not available and clicking Add Agent takes you directly to the agent configuration page.
4. On the Configure Ingestion page, do the following and click Next.
   • Name this Ingestion: Enter a unique recognizable name for this ingestion pipeline.
   • Agent Setup: Configure core parameters for metadata extraction. The following fields are available:

     Field	Default	Description
     Default Owner	—	Owner applied to all entities when no specific level owner is configured. Accepts a user or team name/email.
     Service Owner	—	Owner assigned to the service entity.
     Database Owner	—	Owner assigned to all ingested databases. Accepts a single owner or a per-database name mapping.
     Database Schema Owner	—	Owner assigned to all ingested schemas. Accepts a single owner or a per-schema name mapping.
     Table Owner	—	Owner assigned to all ingested tables. Accepts a single owner or a per-table name mapping.
     Enable Inheritance	On	When on, child entities inherit the owner from their parent when they have no owner configured.
     Query Log Duration	1	Number of days to look back in query logs when processing stored procedure results.
     Query Parsing Timeout Limit	300	Timeout in seconds for parsing a single query.
     Number of Threads	1	Number of threads to use for parallel table ingestion.
     Incremental Extraction	Off	When enabled, subsequent runs only extract entities changed since the last successful run.
     Successful Pipeline Run Lookback Days	7	Number of days to search back for a prior successful run to use as a baseline for incremental extraction.
     Safety Margin Days	1	Additional days added to the baseline timestamp as a buffer for incremental extraction.
     JSON Schema Sample Size	10	Number of rows sampled to infer JSON column schema. Only applies when Extract JSON Schema is enabled in Advanced Config.

     
   • Filter Patterns: Apply include or exclude rules to scope which databases, schemas, tables, and stored procedures this agent ingests. For more information about various filter options, see Step 6: Configure Ingestion Options.
   • Scope & Behaviour: Control how the agent handles metadata during ingestion. Toggle each option on or off based on your needs:

     Toggle	Default	Description
     Include Tables	On	Ingest table metadata from the source. Turn off to skip tables entirely.
     Include Tags	On	Ingest tags from the source.
     Include Stored Procedures	On	Ingest stored procedure metadata.
     Include DDL Statements	Off	Ingest DDL statements alongside table metadata.
     Include Owners	Off	Assign owners to ingested entities when the source owner’s email matches a user in OpenMetadata. Does not overwrite an existing owner.
     Include Custom Properties	Off	Ingest connector-specific custom properties onto entities.
     Mark Deleted Tables	On	Soft-delete tables in OpenMetadata when they are removed from the source. Applies only within the currently ingested schema.
     Mark Deleted Stored Procedures	On	Soft-delete stored procedures in OpenMetadata when they are removed from the source.
     Mark Deleted Schemas	Off	Soft-delete schemas and all their child assets when removed from the source.
     Mark Deleted Databases	Off	Soft-delete databases and all their child assets when removed from the source.
     Override Metadata	Off	When on, source values overwrite existing descriptions, tags, owners, and display names in OpenMetadata. When off, OpenMetadata only updates fields that have no existing value.
     Enable Debug Log	Off	Sets the ingestion log level to DEBUG. Useful for troubleshooting.

     Available toggles vary by connector. Stored procedure options only appear for connectors that support stored procedures.
     
   • Advanced Config: Optional connector-specific settings such as Include Views and Extract JSON Schema.
5. On the Schedule Interval page, set when the agent runs:
   • Schedule: Choose a preset interval (Hourly, Daily, Weekly, Monthly) or enter a custom cron expression.
   • On-Demand: No automatic schedule; trigger the agent manually when needed.
   
6. Click Add to deploy the agent.

​

Related