Trino / Starburst

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.

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.

Setup

1. 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.

2. Source, confirm Trino / Starburst is selected and click Continue.

3. Auth method, pick one of the methods above and click Continue.

4. Authenticate, fill in the Configuration and Credentials fields and click Save credentials, then click Continue.

5. 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.

6. 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.

Connection fields

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

Troubleshooting

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