Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 3 additions & 2 deletions docs-data/property-overrides.json
Original file line number Diff line number Diff line change
Expand Up @@ -1962,7 +1962,8 @@
"xref:manage:tiered-storage.adoc#tiered-storage-versions[]"
],
"version": "v26.2.1",
"config_scope": "topic"
"config_scope": "topic",
"category": "tiered-storage"
},
"redpanda.value.schema.id.validation": {
"description": "Enable validation of the schema ID for values on a record. When enabled, Redpanda validates that the schema ID encoded in the record's value is registered in the Schema Registry according to the configured subject name strategy.",
Expand Down Expand Up @@ -2437,4 +2438,4 @@
"description": "The default write caching mode to apply to user topics. Write caching acknowledges a message as soon as it is received and acknowledged on a majority of brokers, without waiting for it to be written to disk. With `acks=all`, this provides lower latency while still ensuring that a majority of brokers acknowledge the write. \n\nFsyncs follow <<raft_replica_max_pending_flush_bytes,`raft_replica_max_pending_flush_bytes`>> and <<raft_replica_max_flush_delay_ms,`raft_replica_max_flush_delay_ms`>>, whichever is reached first.\n\nThe `write_caching_default` cluster property can be overridden with the xref:reference:properties/topic-properties.adoc#write-caching[`write.caching`] topic property."
}
}
}
}
69 changes: 50 additions & 19 deletions docs-data/redpanda-property-changes-v26.1.14-to-v26.2.1.json
Original file line number Diff line number Diff line change
Expand Up @@ -2,16 +2,16 @@
"comparison": {
"oldVersion": "v26.1.14",
"newVersion": "v26.2.1",
"timestamp": "2026-07-28T16:28:32.194Z"
"timestamp": "2026-07-28T17:34:45.627Z"
},
"summary": {
"newProperties": 26,
"changedDefaults": 4,
"changedDescriptions": 2,
"changedTypes": 2,
"changedDefaults": 6,
"changedDescriptions": 6,
"changedTypes": 4,
"deprecatedProperties": 2,
"removedDeprecatedProperties": 3,
"removedProperties": 0,
"removedDeprecatedProperties": 0,
"removedProperties": 3,
"emptyDescriptions": 2
},
"details": {
Expand Down Expand Up @@ -179,6 +179,11 @@
}
],
"changedDefaults": [
{
"name": "cloud_topics_enabled",
"oldDefault": false,
"newDefault": null
},
{
"name": "default_redpanda_storage_mode_tiered_impl",
"oldDefault": null,
Expand All @@ -198,21 +203,39 @@
"name": "schema_registry_enable_qualified_subjects",
"oldDefault": false,
"newDefault": true
},
{
"name": "space_management_enable_override",
"oldDefault": false,
"newDefault": null
}
],
"changedDescriptions": [
{
"name": "features_auto_enable",
"oldDescription": "Whether new feature flags auto-activate after upgrades (true) or must wait for manual activation via the Admin API (false).",
"newDescription": "Whether features whose `available_policy` is `always` or `new_clusters_only` are auto-activated by the controller after the cluster active logical version reaches their required version. When false, the cluster active version still advances normally, but each such feature must be activated explicitly via the Admin API. Does not affect features with `available_policy::explicit_only`, which always require explicit activation."
"name": "cloud_topics_enabled"
},
{
"name": "schema_registry_enable_qualified_subjects",
"oldDescription": "Enable parsing of qualified subject syntax (:.context:subject). When false, subjects are treated literally, as subjects in the default context. When true, qualified syntax is parsed to extract context and subject.",
"newDescription": "Enable parsing of qualified subject syntax (:.context:subject). When true, qualified syntax is parsed to extract context and subject. When false, subjects are treated literally, as subjects in the default context."
"name": "features_auto_enable"
},
{
"name": "redpanda.storage.mode"
},
{
"name": "redpanda.storage.mode.impl"
},
{
"name": "schema_registry_enable_qualified_subjects"
},
{
"name": "space_management_enable_override"
}
],
"changedTypes": [
{
"name": "cloud_topics_enabled",
"oldType": "boolean",
"newType": "object"
},
{
"name": "log_retention_ms",
"oldType": "retention_duration_property",
Expand All @@ -222,36 +245,44 @@
"name": "retention.ms",
"oldType": "retention_duration_property",
"newType": "object"
},
{
"name": "space_management_enable_override",
"oldType": "boolean",
"newType": "object"
}
],
"deprecatedProperties": [
{
"name": "cloud_topics_enabled",
"reason": "Property marked as deprecated"
"name": "cloud_topics_enabled"
},
{
"name": "space_management_enable_override",
"reason": "Property marked as deprecated"
"name": "space_management_enable_override"
}
],
"removedDeprecatedProperties": [
"removedDeprecatedProperties": [],
"removedProperties": [
{
"name": "log_eviction_exempt_topics",
"type": "array",
"description": "A list of topics in the kafka namespace whose local log is exempt from any form of data deletion: retention settings, local retention for topics with Tiered Storage enabled, and disk space management never remove their data from local disk, and partition moves always deliver the full log to the new replica. Does not affect topic deletion via the Kafka API (see kafka_nodelete_topics)."
"default": [
"_schemas"
],
"description": "A list of topics in the `kafka` namespace whose local log is exempt from any form of data deletion: retention settings, local retention for topics with Tiered Storage enabled, and disk space management never remove their data from local disk, and partition moves always deliver the full log to the new replica. Does not affect topic deletion via the Kafka API (see xref:reference:properties/cluster-properties.adoc#kafka_nodelete_topics[`kafka_nodelete_topics`])."
},
{
"name": "schema_registry_deferred_recovery",
"type": "boolean",
"default": true,
"description": "Defer schema compilation during Schema Registry startup, then compile the loaded schemas in parallel across cores. If disabled, every replayed record is compiled sequentially during the replay."
},
{
"name": "schema_registry_replay_on_startup",
"type": "boolean",
"default": false,
"description": "Replay the internal `_schemas` topic into the store at Schema Registry start-up instead of lazily on the first request. Makes recovery time predictable and keeps the first request from blocking behind a full replay."
}
],
"removedProperties": [],
"emptyDescriptions": [
{
"name": "redpanda.remote.allowgaps",
Expand Down
Loading
Loading