Starburst and Apache Iceberg: OLake Go setup
Starburst runs on Trino. It reads the Iceberg tables OLake Go writes with the same delete-format rules.
Short answer. To query replicated data in Starburst, run OLake Go with AWS Glue, Polaris or Amazon S3 Tables as the Iceberg catalog, and add that catalog in Starburst Galaxy or Starburst Enterprise. Positional and equality deletes work on every release. Deletion vectors need a release based on Trino 480 or later.
Key takeaways
- Starburst runs on Trino and reads OLake Go tables with the same delete-format rules.
- It reads AWS Glue directly, and Polaris and S3 Tables as public preview catalogs in Galaxy.
- Deletion vectors need a Starburst release based on Trino 480 or later.
Last reviewed October 2026.
How OLake Go gets data into Starburst
OLake Go uses change data capture (CDC) where the source has it. It commits Iceberg tables to the catalog. Starburst reads AWS Glue directly, and Polaris and S3 Tables as public preview catalogs in Galaxy.
No guide on this site runs Starburst yet. The Trino page lists runs that use the same connector rules.
When to use it
- Your team already queries through Starburst Galaxy or Starburst Enterprise.
- The tables are on AWS and registered in Glue.
When not to use it
- You run Lakekeeper on S3 and use Galaxy. Galaxy supports Lakekeeper on Azure storage only.
- You need Polaris or S3 Tables in Galaxy for production. Both are public preview there.
Catalogs Starburst reads
| Catalog | Starburst reads | How |
|---|---|---|
| AWS Glue | Yes | Glue catalog |
| Apache Polaris | Yes | Polaris catalog (public preview in Galaxy) |
| Lakekeeper | Partial | Galaxy supports Lakekeeper on Azure storage only |
| Amazon S3 Tables | Yes | S3 Tables (public preview in Galaxy) |
Delete formats Starburst reads
| Equality deletes (v2) | Positional deletes (v2) | Deletion vectors (v3) |
|---|---|---|
| Yes | Yes | Partial |
Starburst follows Trino: v2 deletes everywhere, deletion vectors on releases based on Trino 480 or later. Set Starburst as a target query engine on the OLake Go job and OLake Go picks a format it reads; with Starburst as the only reader that is positional deletes (v2).
Sources: Starburst Galaxy: catalogs (checked 2026-10-12).
Tested guides for Starburst
No guide ends in Starburst yet.
Frequently asked questions
Does Starburst read Iceberg deletion vectors?
On releases based on Trino 480 or later.
Which catalogs does Starburst Galaxy read?
AWS Glue, Polaris (public preview), Amazon S3 Tables (public preview), and Lakekeeper on Azure storage.
Is there a tested Starburst guide?
Not yet. The Trino runs on this site use the same connector. See the Trino page.