Starburst Trino OCF Connector: Overview

Alation Cloud Service Applies to Alation Cloud Service instances of Alation

Customer Managed Applies to customer-managed instances of Alation

The OCF Connector for Starburst Trino was developed by Alation and is available on demand as a Zip file.

To download the Starburst Trino OCF connector package, go to the Alation Connector Hub available from the Customer Portal. Go to Customer Portal > Connectors > Alation Connector Hub. Only Alation users with access to the Customer Portal can access the Alation Connector Hub. If you don’t have access to the Customer Portal, contact Alation Support.

This connector can be used to catalog Starburst Trino assets in Alation. ​​The connector catalogs such objects as schemas, tables, columns, and views. It enables end-users to search and find Starburst Trino objects from the Alation user interface.

Team

You will need the assistance of your DBA to configure this data source.

Starburst Trino administrator:

  • Creates a service account for Alation and grants it the privileges for metadata extraction (MDE), sampling and profiling, and query log ingestion (QLI).

  • Provides a JDBC URI to access metadata.

  • Provides authentication information for Kerberos authentication.

  • Provides the SSL certificate.

Alation Server Admin:

  • Installs the connector.

  • Creates and configures a Starburst Trino data source.

  • Tests the connection and performs extraction, preparing the data source for catalog users.

Scope

The table below lists the catalog functionality supported by the connector.

Feature

Scope

Availability

Authentication

Basic authentication

Authentication with a service account created on the database that uses a username and password

Yes

LDAP

Authentication with a database service account that is an LDAP account in an organization’s network

No

SSL

Database connection over SSL

Yes

Kerberos

Support for Kerberos authentication

Yes

Keytab

Support for Kerberos with keytabs

Yes

SSO

SSO authentication via an identity provider application

No

Metadata Extraction (MDE)

Default MDE

Extraction of metadata based on default extraction queries in the connector code

Yes

Custom query-based MDE

Extraction of metadata based on extraction queries provided by a user

No

Popularity

Indicator of the popularity (intensity of use) of a data object, such as a table or a column

Yes

Extracted metadata objects

Schemas

List of schemas

Yes

Tables

List of tables

Yes

Columns

List of columns

Yes

Column data types

Column data types

Yes

Views

List of views

Yes

Source comments

Source comments

  • Source comments for table objects are not extracted.

  • Source comments for column objects are extracted.

  • Comments can’t be added for schemas (not supported in (Trino)

Yes

Primary keys

Primary key information for extracted tables

No

Foreign keys

Foreign key information for extracted tables

No

Functions

Function metadata

No

Sampling and Profiling

Table sampling

Retrieval of data samples from extracted tables

Yes

Column sampling

Retrieval of data samples from extracted columns

Yes

Deep column profiling

Profiling of columns with the calculation of value distribution stats

Yes

Dynamic profiling

Ability for individual users to connect with their own database accounts to retrieve table and column samples and profiles

Yes

Custom query-based table sampling

Ability to use custom queries for sampling specific tables

Yes

Custom query-based column sampling

Ability to use custom queries for profiling specific columns

Yes

Query Log Ingestion (QLI)

Table-based QLI

Ingestion of query history based on a table or view that contains query history data

Yes

Query-based QLI

Ingestion of query history based on a custom query history extraction query

Yes

JOINs and filters

Calculation of JOIN and filter information based on ingested query history

Yes

Predicates

Ability to parse predicates in ingested queries

Yes

Lineage

Automatic lineage generation

Auto-calculation of lineage based on query history ingested from QLI, MDE, and Compose queries

** View SQL is not extracted during MDE. As a result, lineage information will not be available for views ingested during MDE. Lineage for views will be available from ingesting DDL queries during QLI or from Compose.

Yes**

Direct lineage

Direct lineage relies on metadata extraction (MDE) and does not require query log ingestion (QLI).

No

Compose

Customer-managed (on-prem) Alation instances

Compose on on-prem Alation instances

Yes

Alation Cloud Service instances

Depending on your network configuration, you may be using Alation Agent to connect to your data source.

Compose with Agent is supported from connector version 1.1.0.4553.

Yes

Basic authentication in Compose

Authentication in Compose with username and password of a user account

Yes

SSO authentication in Compose

Authentication in Compose with SSO credentials

No

Limitations

  • Kerberos authentication is not supported in Compose (Compose is not available for a kerberized database).

  • Custom query-based metadata extraction is currently not supported for this data source.

  • The profiling query templates for profiling numeric and non-numeric columns on the Custom Settings tab of the data source Settings page are currently not supported for this data source.