This is an automated email from the ASF dual-hosted git repository.
weichiu pushed a commit to branch HDDS-9225-website-v2
in repository https://gitbox.apache.org/repos/asf/ozone-site.git
The following commit(s) were added to refs/heads/HDDS-9225-website-v2 by this
push:
new 66e8d375c Addendum for HDDS-14302.
66e8d375c is described below
commit 66e8d375ca107c7829b3cb92b3d1e90ee11d647c
Author: Wei-Chiu Chuang <[email protected]>
AuthorDate: Mon Feb 9 10:34:52 2026 -0800
Addendum for HDDS-14302.
---
cspell.yaml | 2 ++
docs/04-user-guide/03-integrations/03-iceberg.md | 8 +++++---
2 files changed, 7 insertions(+), 3 deletions(-)
diff --git a/cspell.yaml b/cspell.yaml
index b16de6b38..fd8cd9549 100644
--- a/cspell.yaml
+++ b/cspell.yaml
@@ -181,6 +181,7 @@ words:
- devs
- CLI
- lakehouse
+- lakehouses
- Flink
- rebalancing
- JDK
@@ -203,6 +204,7 @@ words:
- minimises
- minimising
- tarballed
+- Namenodes
# Apache Ozone community member names
- Sumit
# Company names for "Who Uses Ozone" page
diff --git a/docs/04-user-guide/03-integrations/03-iceberg.md
b/docs/04-user-guide/03-integrations/03-iceberg.md
index 975aed15b..e870983d8 100644
--- a/docs/04-user-guide/03-integrations/03-iceberg.md
+++ b/docs/04-user-guide/03-integrations/03-iceberg.md
@@ -9,6 +9,7 @@ sidebar_label: Iceberg
Iceberg uses Ozone storage layer to build scalable data lakehouses, acting as
the durable system of record for table data and metadata. Ozone’s native atomic
rename capability supports Iceberg’s atomic commit requirements, providing
strong consistency for data management without external locking services.
Ozone's ability to handle high object counts and its strong consistency model
(via Ratis) make it a suitable, reliable backend for Iceberg's transactional,
snapshot-based structure.
## Key Integration Details
+
- **Storage and Metadata Management:** Iceberg stores data files and metadata
files (manifests, snapshots) directly on Ozone.
- **Atomic Operations:** Ozone supports necessary atomic operations for
Iceberg’s commit process, ensuring data consistency during concurrent writes.
- **Performance:** The combination allows for petabyte-scale analytics and
fast query planning, overcoming the scalability bottlenecks of traditional HDFS
Namenodes.
@@ -21,14 +22,15 @@ This tutorial shows how to get started with Apache Iceberg
to Apache Ozone using
### Quickstart environment
- Unsecure Ozone and Iceberg clusters.
-- Ozone S3G enables virtual-host style addressing with a subdomain `s3.ozone`.
+- Ozone S3G enables virtual-host style addressing with a subdomain `s3.ozone`.
- The subdomain and the subdomain with the bucket name `warehouse.s3.ozone`
are mapped to the S3 Gateway.
- Iceberg accesses Ozone via S3 Gateway.
### Step 1 — Create `docker-compose.yaml` for Ozone services
Create a `docker-compose.yaml` file with the following content to
-- Spin up a single datanode Ozone cluster
+
+- Spin up a single Datanode Ozone cluster
- Start the S3 Gateway with the required configurations for Iceberg
- Wait for OM to be ready before starting
- Create the bucket `warehouse` on startup
@@ -257,4 +259,4 @@ Verify data files are stored in Ozone S3:
docker compose exec -it s3g ozone fs -ls -R ofs://om/s3v/warehouse
```
-Spark UI is available at `http://localhost:8080`. You can monitor the Spark
jobs here.
\ No newline at end of file
+Spark UI is available at `http://localhost:8080`. You can monitor the Spark
jobs here.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
