This page compares Query Engine with the Apache Iceberg specification and the features listed on Iceberg’s implementation status page. Read means Query Engine can query tables that use the feature. Write means Query Engine can create or change them. SQL commands and procedures follow the syntax in Iceberg’s Spark docs.
To set up an Iceberg catalog, see Table formats.
Yes Supported Partial Supported with limits No Not supported yet
Summary
Table spec features
Rows follow the Apache Iceberg table spec and concept docs. Spec = format version that introduced it; — = not tied to one version.
Schemas and evolution
Partitioning
Sort orders
Row-level changes and lineage
Snapshots and references
Statistics and encryption
Data types
Full type list from the Iceberg spec and Implementation status page.
Primitive
Date and time
Nested and semi-structured
Geospatial and other
DDL
Commands as documented in Iceberg’s Spark DDL docs. If e6data supports the capability with different syntax, mark Yes and note the syntax.
Create, replace and drop
ALTER TABLE: table and columns
ALTER TABLE: partitioning, ordering, identifiers
Views (Iceberg view spec)
DML
Writes
Branch writes and concurrency
Reads and time travel
Procedures and maintenance
Procedures as documented in Iceberg’s Spark procedures docs (CALL catalog.system.<name>). An equivalent command in e6data counts as Yes; note the syntax.
Snapshot management
Table migration
Catalog implementations
Catalogs documented by Apache Iceberg. Third-party catalogs that speak the REST spec (e.g. Polaris, Gravitino, Lakekeeper) count under REST.
REST catalog operations
Operations listed on the Iceberg Implementation status page and REST Catalog spec.
Namespace operations
Table operations
View operations
Other REST capabilities
File IO
Storage backends from the Implementation status page.
Last modified on October 15, 2026