> For the complete documentation index, see [llms.txt](https://v2.dataos.info/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://v2.dataos.info/concepts/resources/depot/supported-table-format/iceberg.md).

# Iceberg

In DataOS, object storage Depots (ABFSS, Amazon S3, GCS) support two table formats: `iceberg` and `delta`. This section covers the Iceberg table format.

### What does the Iceberg table format actually do? <a href="#what-does-the-iceberg-table-format-actually-do" id="what-does-the-iceberg-table-format-actually-do"></a>

The Iceberg format manages both the data (Parquet/ORC/Avro files) and the metadata (schemas, snapshots, partitions) in a structured, versioned layout across object storage. Here's how it works behind the scenes:

| Layer          | What It Does                                                                          |
| -------------- | ------------------------------------------------------------------------------------- |
| **Data Layer** | Stores actual data files (e.g., Parquet). Immutable and columnar for efficient reads. |

\| **Metadata Layer** | Tracks schema, partitions, file locations, and snapshot history. Enables version control, rollback, and optimization. |

\| **Catalog Layer** | Provides a central registry to discover and access tables. Maps table names to metadata locations. |

With this layered architecture, Iceberg provides:

* Atomic operations for inserts, deletes, and updates, even across multiple partitions.
* **Schema evolution**: add, drop, or rename columns without rewriting data.
* **Partition evolution**: change the partition strategy over time with zero rewrites.
* **Snapshot-based time travel**: query your data as it existed at any point in the past.
* **Efficient metadata pruning**: scan only the relevant files for each query.

Iceberg separates metadata from compute, so multiple engines (such as Spark and Trino) can read and write the same dataset concurrently and safely.

### Supported object storage sources in DataOS <a href="#supported-object-storage-sources-in-dataos" id="supported-object-storage-sources-in-dataos"></a>

DataOS supports the Iceberg table format on the following object storage Depots:

* [ABFSS](/concepts/resources/depot/supported-sources/abfss.md)
* [Amazon S3](/concepts/resources/depot/supported-sources/s3.md)
* [GCS](/concepts/resources/depot/supported-sources/gcs.md)

For each of these storage types, create a Depot with `format: iceberg` to use Iceberg table management in DataOS.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://v2.dataos.info/concepts/resources/depot/supported-table-format/iceberg.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.