Trino / Starburst¶

Connect Adverity Atlas to Trino, Starburst Enterprise, or Starburst Galaxy.

Prerequisites¶

A user or role that can read the data you want to query. Adverity Atlas only issues read queries against your tables, it does not create, modify, or drop them, so read access is all it needs.

What Adverity Atlas reads¶

A sync lists the objects in each schema you bind and records what kind each one is. Profiling then runs aggregate queries over the types it can profile, and those field statistics are what Chat and the glossary work from. An object that is discovered but not profiled is still queryable, it just carries no statistics.

Object type	Discovered and queryable	Profiled
Tables	Yes	Yes
Views	Yes	No

Querying and profiling need the same access: SELECT on the objects you want available. Profiling adds no privilege of its own, it reads the same objects with aggregate queries. The Connection test on the wizard’s Test step proves exactly that access, in the order a sync needs it: connect, list the schemas, list the tables in the target schema, and read a row.

Authentication methods¶

Trino / Starburst supports 3 authentication methods. Choose the one that matches your security posture.

Username & Password¶

Basic authentication over HTTPS, covers Starburst Galaxy and Enterprise LDAP.

Best for: Starburst Galaxy, and Enterprise deployments behind LDAP.

Credentials:

Field	Description
Username	e.g. `analyst@example.com`	Required
Password	Stored encrypted.	Required

JWT Token¶

Authenticate with a pre-issued JWT bearer token over HTTPS.

Best for: Environments that issue short-lived bearer tokens.

Credentials:

Field	Description
JWT Token	e.g. `eyJhbGciOi...` Stored encrypted.	Required
Username (optional)	e.g. `analyst@example.com`	Optional

OAuth 2.0 (client credentials)¶

Machine-to-machine OAuth: exchange a client id and secret for a bearer token at an IdP token endpoint.

Best for: Machine-to-machine auth against an IdP.

Credentials:

Field	Description
Token URL	e.g. `https://idp.example.com/oauth2/token`	Required
Client ID		Required
Client Secret	Stored encrypted.	Required
Scope (optional)		Optional

Setup¶

Go to Settings > Data Governance > Data Sources. Under Add Connection, choose Trino / Starburst. The Add a data source wizard opens and runs in five steps.
Source, confirm Trino / Starburst is selected and click Continue.
Auth method, pick one of the methods above and click Continue.
Authenticate, fill in the Configuration and Credentials fields and click Save credentials, then click Continue.
Test, Adverity Atlas tests the connection as soon as you arrive and shows the result under Connection test. Continue unlocks once the test passes. After fixing a failure, click Test again. Back discards the saved credentials and returns you to Authenticate, with the configuration still filled in.
Review & create, enter a Name, choose a Sync schedule, and pick a Mode: Active (sync runs on schedule and agents can query this source), Development (sync runs, but agents cannot query it yet), or Disabled (no automated operations). Then click Create data source.

The Connection test runs the full connection diagnostic: it authenticates, lists the visible schemas, lists the tables in the target schema, and reads a row. You cannot continue to Review & create until every check passes, so a wrong credential or a missing grant is resolved here rather than becoming an unhealthy source afterwards. A failed check reports the warehouse’s own error, and the grant that is missing where Adverity Atlas can work it out, see Connection diagnostics. A test that could not run at all says “The connection test could not run. Try again in a moment.”

Adverity Atlas verifies the connection as soon as the source is created, and starts the first sync when verification succeeds and the mode allows it. Schema discovery and field profiling run from that sync.

Tip

If someone else holds the credentials, use Share a one-time link under Or ask someone else on the Authenticate step. They submit the credentials through that link and see the connection test run on their page too. If it fails, Provide credentials again lets them correct what they entered. Your wizard moves on to Test once they submit, so the secret never passes through you.

Connection fields¶

These appear under Configuration on the wizard’s Authenticate step.

Field	Description
Host	e.g. `my-cluster.trino.galaxy.starburst.io`	Required
Port	e.g. `443`	Optional
Catalog	e.g. `hive`	Required
Schema	e.g. `default`	Optional
Role (Starburst Galaxy)	e.g. `accountadmin`	Optional

Troubleshooting¶

Symptom	Likely cause
401 Unauthorized	Wrong credentials, or the token expired. JWTs are not refreshed automatically.
“Catalog does not exist”	The catalog name is wrong or not visible to the role.
Starburst Galaxy connection fails	Galaxy requires the Role field and TLS on port 443.

What’s next?¶

Configure the glossary, align the language across your platforms so answers use your definitions
Ask questions about your data, start a conversation against the data you just connected
Data sources, schema discovery, profiling, and managing connections