[26.2] Schema context support for Iceberg translation#1784
Conversation
✅ Deploy Preview for redpanda-docs-preview ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
0734ec9 to
e53e23a
Compare
|
|
||
| == Iceberg translation with Schema Registry contexts | ||
|
|
||
| Iceberg-enabled topics can now resolve schemas from a specific xref:manage:schema-reg/schema-reg-contexts.adoc[Schema Registry context] instead of always using the default context. Set the new `redpanda.schema.registry.context` topic property to bind a topic's Iceberg translation to a context, useful for multi-tenant or per-environment schema isolation. |
There was a problem hiding this comment.
Probably better split into two sentences
| // tag::category-schema-registry[] | ||
| === redpanda.schema.registry.context | ||
|
|
||
| The xref:manage:schema-reg/schema-reg-contexts.adoc[Schema Registry context] Redpanda uses to resolve schema IDs for records in this topic, for example when translating the topic to an Iceberg table. Defaults to the Schema Registry default context (`.`). |
There was a problem hiding this comment.
Technically not always true I think. It uses the context to resolve either the schema ID or the name of the schema depending on the iceberg translation mode. Cc @wdberkeley
| [[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 schema IDs referenced by records in the topic against the configured context instead of the default context (`.`). |
There was a problem hiding this comment.
Same comment here. Resolves "schemas" is probably better catch all . Sometimes it looks up by ID in a context and sometime by name @kbatuigas
3 participants
Description
This pull request introduces support for resolving Iceberg-enabled topic schemas within specific Schema Registry contexts, rather than always using the default context. It adds a new topic property,
redpanda.schema.registry.context, and updates documentation to reflect this new capability, which is especially useful for multi-tenant or per-environment schema isolation. Related troubleshooting guidance and configuration documentation have also been updated.Iceberg and Schema Registry context support:
redpanda.schema.registry.contexttopic property, allowing topics to bind Iceberg translation to a specific Schema Registry context for schema resolution.Resolves https://redpandadata.atlassian.net/browse/DOC-2192
Review deadline: 23 Jul
Preview pages
Checks