Skip to content

Commit 4198e5c

Browse files
kbatuigasFeediver1
andauthored
Update modules/manage/pages/iceberg/about-iceberg-topics.adoc
Co-authored-by: Joyce Fee <102751339+Feediver1@users.noreply.github.com>
1 parent 2f7a519 commit 4198e5c

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

modules/manage/pages/iceberg/about-iceberg-topics.adoc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -79,7 +79,7 @@ endif::[]
7979

8080
. Set the `iceberg_enabled` configuration option on your cluster to `true`.
8181
+
82-
When multiple clusters write to the same catalog, each cluster must use a distinct namespace to avoid table name collisions. This is especially critical for REST catalog providers that offer a single global catalog per account (such as AWS Glue), where there is no other isolation mechanism. By default, Redpanda creates Iceberg tables in a namespace called `redpanda`. To use a unique namespace for your cluster's REST catalog integration, also set config_ref:iceberg_default_catalog_namespace,true,properties/cluster-properties[`iceberg_default_catalog_namespace`] when you set `iceberg_enabled`. This property cannot be changed after you enable Iceberg topics on the cluster.
82+
When multiple clusters write to the same catalog, each cluster must use a distinct namespace to avoid table name collisions. This is especially critical for REST catalog providers that offer a single global catalog per account (such as AWS Glue), where there is no other isolation mechanism. By default, Redpanda creates Iceberg tables in a namespace called `redpanda`. To use a unique namespace for your cluster's REST catalog integration, also set config_ref:iceberg_default_catalog_namespace,true,properties/cluster-properties[`iceberg_default_catalog_namespace`] when you set `iceberg_enabled`. You cannot change this property after you enable Iceberg topics on the cluster.
8383
ifdef::env-cloud[]
8484
+
8585
[tabs]

0 commit comments

Comments
 (0)