From 3f9929ebb2e4e898c27c19a2bc4b54516eba4318 Mon Sep 17 00:00:00 2001 From: Kat Batuigas Date: Thu, 30 Jul 2026 16:18:56 -0700 Subject: [PATCH 1/4] 26.2 Cloud: decoded keys and headers (Iceberg) --- modules/manage/pages/iceberg/specify-iceberg-schema.adoc | 9 +++++++-- 1 file changed, 7 insertions(+), 2 deletions(-) diff --git a/modules/manage/pages/iceberg/specify-iceberg-schema.adoc b/modules/manage/pages/iceberg/specify-iceberg-schema.adoc index 17c27d5172..8de7de09a5 100644 --- a/modules/manage/pages/iceberg/specify-iceberg-schema.adoc +++ b/modules/manage/pages/iceberg/specify-iceberg-schema.adoc @@ -120,10 +120,14 @@ value_schema_latest:subject=,protobuf_name=>, `redpanda.iceberg.mode` also accepts a section-based syntax that lets you independently configure how Redpanda translates the record key, value, and headers into the Iceberg table. The `key_value`, `value_schema_id_prefix`, and `value_schema_latest` modes are shorthand for common combinations of these sections (see <>). +endif::[] +ifdef::env-cloud[] +In addition to the <>, `redpanda.iceberg.mode` also accepts a section-based syntax that lets you independently configure how Redpanda translates the record key, value, and headers into the Iceberg table. The `key_value`, `value_schema_id_prefix`, and `value_schema_latest` modes are shorthand for common combinations of these sections (see <>). +endif::[] The `key` and `headers` sections change fields inside the `redpanda` system struct column (`redpanda.key` and the `value` field of each entry in `redpanda.headers`), while the `value` section changes the columns outside that struct. See <> for the base row structure that every generated table includes. @@ -369,6 +373,7 @@ Redpanda rejects the following configurations when you create or alter a topic: NOTE: Option values cannot contain `,` or `;`, and whitespace is not trimmed. Avoid extra spaces around subject names or Protobuf message names. // Broker-upgrade gating not applicable in RP Cloud +ifndef::env-cloud[] [IMPORTANT] ==== Configuring anything beyond `key:mode=binary` and `headers:value_type=binary` requires every broker in the cluster to be running Redpanda version 26.2 or later. Until all brokers are upgraded, Redpanda rejects these configurations with an error. @@ -380,6 +385,7 @@ The following configurations require all brokers to be running version 26.2 or l * `value:layout=nested` * `value:mode=string` ==== +endif::[] === Example configurations @@ -423,7 +429,6 @@ rpk topic describe orders -c | grep redpanda.iceberg.mode ---- NOTE: If a section-based configuration is equivalent to one of the modes described in <>, `rpk topic describe` displays it using that mode's name instead of the section syntax. -endif::[] ifndef::env-cloud[] [[resolve-schemas-within-a-context]] From e9eedffa5c36db76f4da11087051ae3a8d781f2b Mon Sep 17 00:00:00 2001 From: Kat Batuigas Date: Thu, 30 Jul 2026 16:35:53 -0700 Subject: [PATCH 2/4] DOC-2311 --- modules/manage/pages/iceberg/specify-iceberg-schema.adoc | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/modules/manage/pages/iceberg/specify-iceberg-schema.adoc b/modules/manage/pages/iceberg/specify-iceberg-schema.adoc index 8de7de09a5..fe6b5b2125 100644 --- a/modules/manage/pages/iceberg/specify-iceberg-schema.adoc +++ b/modules/manage/pages/iceberg/specify-iceberg-schema.adoc @@ -430,7 +430,6 @@ rpk topic describe orders -c | grep redpanda.iceberg.mode NOTE: If a section-based configuration is equivalent to one of the modes described in <>, `rpk topic describe` displays it using that mode's name instead of the section syntax. -ifndef::env-cloud[] [[resolve-schemas-within-a-context]] == Resolve schemas within a Schema Registry context @@ -438,7 +437,12 @@ If you use xref:manage:schema-reg/schema-reg-contexts.adoc[Schema Registry conte Both modes rely on a schema registered in Schema Registry to determine the Iceberg table structure. +ifndef::env-cloud[] Starting in Redpanda 26.2, Schema Registry contexts are enabled by default. See xref:manage:schema-reg/schema-reg-contexts.adoc[Schema Registry contexts] to learn about contexts and qualified subject naming before you configure this property. +endif::[] +ifdef::env-cloud[] +Schema Registry contexts are enabled by default. See xref:manage:schema-reg/schema-reg-contexts.adoc[Schema Registry contexts] to learn about contexts and qualified subject naming before you configure this property. +endif::[] .Set the Schema Registry context on a new topic [,bash] @@ -467,7 +471,6 @@ To change the Schema Registry context on a topic that is actively translating to . Change `redpanda.schema.registry.context`. . Re-enable Iceberg translation. ==== -endif::[] == How Iceberg modes translate to table format From e0a2c28adf210ec0d4eb5b389a578ec01ca37032 Mon Sep 17 00:00:00 2001 From: Kat Batuigas Date: Thu, 30 Jul 2026 16:36:08 -0700 Subject: [PATCH 3/4] DOC-2290 --- modules/develop/pages/kafka-clients.adoc | 15 --------------- 1 file changed, 15 deletions(-) diff --git a/modules/develop/pages/kafka-clients.adoc b/modules/develop/pages/kafka-clients.adoc index 1ca54be6af..5249f5591c 100644 --- a/modules/develop/pages/kafka-clients.adoc +++ b/modules/develop/pages/kafka-clients.adoc @@ -18,12 +18,7 @@ Use this reference to: == Kafka client compatibility -ifndef::env-cloud[] Redpanda validates the Apache Kafka Java client and a set of widely used non-Java clients, at their current versions that support Kafka 4.x, using the ducktape and chaos test suites. Validation confirms connectivity and correctness across core Kafka APIs, such as produce, consume, and transaction operations, at current client versions. Modern clients auto-negotiate protocol versions or use an earlier protocol version accepted by Redpanda brokers. -endif::[] -ifdef::env-cloud[] -Clients developed for Kafka versions 0.11 or later are compatible with Redpanda. The Apache Kafka Java client at version 4.x is validated against Redpanda using the ducktape and chaos test suites; other clients in the table here remain compatible with the Kafka protocol versions they have always supported. Modern clients auto-negotiate protocol versions or use an earlier protocol version accepted by Redpanda brokers. -endif::[] TIP: Always use the latest supported version of a Kafka client. @@ -39,25 +34,15 @@ The following clients have been validated with Redpanda. | https://github.com/confluentinc/librdkafka[librdkafka^] | Go -ifndef::env-cloud[] a| * https://github.com/twmb/franz-go[franz-go^] * https://github.com/confluentinc/confluent-kafka-go[confluent-kafka-go^] * https://github.com/IBM/sarama[Sarama^] -endif::[] -ifdef::env-cloud[] -| https://github.com/twmb/franz-go[franz-go^] -endif::[] | Python -ifndef::env-cloud[] a| * https://github.com/dpkp/kafka-python[kafka-python^] * https://github.com/confluentinc/confluent-kafka-python[confluent-kafka-python^] -endif::[] -ifdef::env-cloud[] -| https://github.com/dpkp/kafka-python[kafka-python^] -endif::[] | Rust | https://github.com/kafka-rust/kafka-rust[kafka-rust^] From 058d10e2c99e02b40a16bb37114dcd40ed7db180 Mon Sep 17 00:00:00 2001 From: Kat Batuigas <36839689+kbatuigas@users.noreply.github.com> Date: Tue, 4 Aug 2026 11:12:13 -0700 Subject: [PATCH 4/4] Update modules/manage/pages/iceberg/specify-iceberg-schema.adoc --- modules/manage/pages/iceberg/specify-iceberg-schema.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/modules/manage/pages/iceberg/specify-iceberg-schema.adoc b/modules/manage/pages/iceberg/specify-iceberg-schema.adoc index fe6b5b2125..4438c41232 100644 --- a/modules/manage/pages/iceberg/specify-iceberg-schema.adoc +++ b/modules/manage/pages/iceberg/specify-iceberg-schema.adoc @@ -433,7 +433,7 @@ NOTE: If a section-based configuration is equivalent to one of the modes describ [[resolve-schemas-within-a-context]] == Resolve schemas within a Schema Registry context -If you use xref:manage:schema-reg/schema-reg-contexts.adoc[Schema Registry contexts] to isolate schemas (for example, by environment or tenant), set the `redpanda.schema.registry.context` topic property to bind the topic to that context. Redpanda then resolves the schemas referenced by records in the topic against the configured context instead of the default context (`.`). Depending on the topic's Iceberg mode, Redpanda looks up either the schema ID embedded in each record (`value_schema_id_prefix` mode) or the latest schema for a subject (`value_schema_latest` mode) within that context. +If you use xref:manage:schema-reg/schema-reg-contexts.adoc[Schema Registry contexts] to isolate schemas (for example, by environment or tenant), set the `redpanda.schema.registry.context` topic property to bind the topic to that context. Redpanda then resolves the schemas referenced by records in the topic against the configured context instead of the default context (`.`). This applies to all schema-decoding modes, for both keys and values: the `value_schema_id_prefix` and `value_schema_latest` shorthand modes, and any `key` or `value` section that uses `mode=schema_id_prefix` or `mode=schema_latest`. Both modes rely on a schema registered in Schema Registry to determine the Iceberg table structure.