Presto and Apache Iceberg: OLake Go setup
Presto reads Iceberg tables through its Iceberg connector. What it can read depends on whether the workers are Java or native C++.
Short answer. To query replicated data in Presto, run OLake Go with AWS Glue, Polaris, Lakekeeper, Hive Metastore or Nessie as the Iceberg catalog, and configure the Presto Iceberg connector for it. Positional deletes work on both worker types. Add Presto as a target query engine and OLake Go writes positional deletes.
Key takeaways
- Presto reads OLake Go tables through its Iceberg connector on Glue, Polaris, Lakekeeper, Hive Metastore or Nessie.
- With Presto as a target query engine, OLake Go writes positional deletes, which Java and native C++ workers both read.
- The Presto lakehouse post shows an earlier end-to-end setup.
Last reviewed October 2026.
How OLake Go gets data into Presto
OLake Go uses change data capture (CDC) where the source has it. It commits Iceberg tables to the catalog. Presto reads Polaris and Lakekeeper as REST (representational state transfer) catalogs, and Glue through the Hive catalog type.
No guide ends in Presto yet. The Presto lakehouse post shows an earlier end-to-end setup.
When to use it
- You already run Presto and want replicated tables beside your existing data.
- The tables are in Glue, Polaris, Lakekeeper, Hive Metastore or Nessie.
When not to use it
- The cluster runs native C++ workers and the tables use equality deletes. Those need Java workers.
- You need deletion vectors on Java workers. Only Presto C++ 0.299 and later reads them.
Catalogs Presto reads
| Catalog | Presto reads | How |
|---|---|---|
| AWS Glue | Yes | Hive catalog type with hive.metastore=glue |
| Apache Polaris | Yes | REST catalog with OAuth2 |
| Lakekeeper | Yes | REST catalog with OAuth2 |
| Nessie | Yes | Nessie catalog |
| Hive Metastore | Yes | Hive Metastore |
Delete formats Presto reads
| Equality deletes (v2) | Positional deletes (v2) | Deletion vectors (v3) |
|---|---|---|
| Partial | Yes | Partial |
Presto reads position deletes on both Java and native workers. Equality deletes need Java workers; deletion vectors only on Presto C++ 0.299 and later. Set Presto as a target query engine on the OLake Go job and OLake Go picks a format it reads; with Presto as the only reader that is positional deletes (v2).
Sources: Presto: Iceberg connector (checked 2026-10-12).
Tested guides for Presto
No guide ends in Presto yet.
Frequently asked questions
Does Presto read equality deletes?
On Java workers only. Positional deletes work on both Java and native workers.
Does Presto read Iceberg deletion vectors?
Only Presto C++ 0.299 and later.
How does Presto connect to AWS Glue?
With the Hive catalog type and hive.metastore=glue.