
Connect Secoda to Starburst to unify metadata across catalogs and schemas, capture lineage from view definitions, and bring metadata and usage insights into your catalog.
Add to Secoda
Starburst is an enterprise data analytics platform built on Trino, the open-source distributed SQL query engine. It allows organizations to query data across multiple sources, from data lakes to warehouses, without moving the data. Starburst extends Trino with enterprise-grade features including multi-cluster support, governance capabilities, performance optimization, and APIs that provide deeper visibility into metadata, lineage, and usage. The Secoda integration with Starburst leverages the Trino integration to ingest and manage this metadata directly in Secoda, giving data teams a single place to search, understand, and discover their Starburst environment.
The Starburst integration can pull metadata from multiple catalogs in your Starburst deployment. Instead of manually setting up separate Trino connections, data teams can consolidate visibility into one platform. This gives users a view of their catalogs, schemas, tables, and views and makes it easier to navigate, discover, and organize data across environments.
Through the Trino-compatible SQL interface, Secoda ingests detailed table and column-level metadata. This includes information such as table and column names, column data types, table and column descriptions, and view definitions. Having this level of detail in Secoda provides context about structure and relationships. It allows teams to understand their data assets and to make better decisions about where to focus documentation and analysis efforts.
When configured with a query history table, the integration can bring in query execution logs from Starburst. This makes it possible to capture which user or service account ran a query, how long the query took, and how frequently it was executed. Over time, Secoda can highlight patterns of usage, the most queried tables, and identify popular assets. This context helps data teams identify critical assets, understand workloads, and prioritize documentation and monitoring for the areas of the business that rely most heavily on Starburst.
Secoda can extract view definitions from Starburst and automatically generate lineage showing how views depend on underlying tables. By ingesting this information into Secoda, users can trace dependencies and understand some of the relationships across their data ecosystem. This view lineage helps with impact analysis, debugging issues, and understanding the flow of data through transformations.
The Starburst integration builds on Secoda's existing Trino connector, providing: - Catalog, schema, table, and view metadata extraction - Column-level details including data types and descriptions - View definition lineage (table-to-view relationships) - Usage statistics when configured with query history tables - Support for excluding specific catalogs via feature flags