# Table Formats

e6data supports table formats that define how data is stored, managed, and queried in a data lake or lakehouse environment. These are the table formats we support, and each table format provides a specific set of features based on its design and capabilities.

These formats offer advanced functionalities such as ACID transactions, schema and partition evolution, time travel, and efficient metadata handling.

| Table Format                                                                 | Description                                                                                                                                                           |
| ---------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| [**Delta Lake**](/product-documentation/table-formats/delta-lake.md)         | Open-source storage layer that brings ACID transactions and scalable metadata handling to data lakes. Ideal for use cases requiring data reliability and consistency. |
| [**Apache Iceberg**](/product-documentation/table-formats/apache-iceberg.md) | High-performance table format built for analytic datasets. Supports schema evolution, partitioning, and time travel without sacrificing performance.                  |
| [**Apache Hudi** ](/product-documentation/table-formats/apache-hudi.md)      | Open-source storage format enabling efficient upserts, incremental processing, and time travel on data lakes.                                                         |


---

# Agent Instructions: 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:

```
GET https://docs.e6data.com/product-documentation/table-formats.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.