Update 26.2 (client compatibility, Iceberg translation) single sourcing for Cloud - #1857
Open
kbatuigas wants to merge 3 commits into
Open
Update 26.2 (client compatibility, Iceberg translation) single sourcing for Cloud#1857kbatuigas wants to merge 3 commits into
kbatuigas wants to merge 3 commits into
Conversation
✅ Deploy Preview for redpanda-docs-preview ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
4 tasks
Contributor
📝 WalkthroughWalkthroughKafka client documentation now uses environment-independent validation text and grouped Go/Python client lists. Iceberg schema documentation now includes translation and Schema Registry context guidance for cloud environments, while broker version gating and version-specific wording remain limited to self-managed deployments. Estimated code review effort: 2 (Simple) | ~10 minutes Suggested reviewers: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@modules/manage/pages/iceberg/specify-iceberg-schema.adoc`:
- Around line 440-445: Update the Schema Registry context guidance in the
env-cloud and non-cloud documentation blocks to explicitly describe whether key
decoding modes schema_id_prefix and schema_latest resolve schemas using the
configured Schema Registry context; if they do, document that lookup behavior
alongside the existing context and qualified-subject explanation.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro
Run ID: 51ad457d-5632-49c5-815f-47a428deb763
📒 Files selected for processing (2)
modules/develop/pages/kafka-clients.adocmodules/manage/pages/iceberg/specify-iceberg-schema.adoc
💤 Files with no reviewable changes (1)
- modules/develop/pages/kafka-clients.adoc
Comment on lines
+440
to
+445
| 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::[] |
Contributor
There was a problem hiding this comment.
🗄️ Data Integrity & Integration | 🟡 Minor | ⚡ Quick win
Document Schema Registry context behavior for key decoding.
This section only names the legacy value modes, while this page now also supports key:mode=schema_id_prefix and key:mode=schema_latest. Clarify whether key schema lookups use the configured context, and document the behavior if they do.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@modules/manage/pages/iceberg/specify-iceberg-schema.adoc` around lines 440 -
445, Update the Schema Registry context guidance in the env-cloud and non-cloud
documentation blocks to explicitly describe whether key decoding modes
schema_id_prefix and schema_latest resolve schemas using the configured Schema
Registry context; if they do, document that lookup behavior alongside the
existing context and qualified-subject explanation.
kbatuigas
commented
Aug 3, 2026
| [[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. |
Contributor
Author
There was a problem hiding this comment.
Suggested change
| 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`. |
@wdberkeley does this change look good per this bot feedback?
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Related: redpanda-data/cloud-docs#657
This pull request updates documentation to unify and clarify instructions for both self-hosted and cloud environments, primarily by removing conditional content that previously differentiated between the two. It also makes version requirements and feature availability clearer for Redpanda features such as Kafka client compatibility and Iceberg schema translation.
Documentation unification and clarification:
env-cloud) conditionals from the Kafka client compatibility section, presenting a single, unified explanation of validated clients and compatibility for both self-hosted and cloud users.Version requirement and feature availability updates:
Resolves https://redpandadata.atlassian.net/browse/
Review deadline:
Page previews
These pages are single-sourced, and this PR contains the source/
env-cloudconditional changes. Review both renderings:Cloud (single-sourced) rendering — for SME review of Cloud accuracy. Built by the tandem cloud-docs PR #657, which pulls this branch and applies the
env-cloudattribute:Self-managed (streaming) rendering:
Checks