Skip to content
16 changes: 9 additions & 7 deletions docs-data/property-overrides.json
Original file line number Diff line number Diff line change
Expand Up @@ -778,7 +778,8 @@
"description": "Set the default storage mode for new topics. This value applies to any topic created without an explicit <<redpandastoragemode,`redpanda.storage.mode`>> setting (that is, when the topic's `redpanda.storage.mode` is `unset`).\n\nAccepted values:\n\n* `unset`: Defer to the legacy <<cloud_storage_enable_remote_read,`redpanda.remote.read`>> and <<cloud_storage_enable_remote_write,`redpanda.remote.write`>> topic properties for Tiered Storage configuration.\n* `local`: Store data only on local disks, with no object storage involvement.\nifndef::env-cloud[]\n* `tiered`: Store data on local disks and replicate it to object storage using xref:manage:tiered-storage.adoc[Tiered Storage]. Equivalent to setting `redpanda.remote.read` and `redpanda.remote.write` to `true`.\n* `cloud`: Store data primarily in object storage using xref:develop:manage-topics/cloud-topics.adoc[Cloud Topics].\nendif::[]\nifdef::env-cloud[]\n* `tiered`: Store data on local disks and replicate it to object storage using Tiered Storage. Equivalent to setting `redpanda.remote.read` and `redpanda.remote.write` to `true`.\n* `cloud`: Store data primarily in object storage using Cloud Topics.\nendif::[]",
"related_topics": [
"self-managed-only: xref:manage:tiered-storage.adoc[Tiered Storage]",
"self-managed-only: xref:develop:manage-topics/cloud-topics.adoc[Manage Cloud Topics]"
"self-managed-only: xref:develop:manage-topics/cloud-topics.adoc[Manage Cloud Topics]",
"cloud-only: xref:develop:topics/cloud-topics.adoc[Manage Cloud Topics]"
],
"config_scope": "cluster",
"version": "v26.1.1"
Expand Down Expand Up @@ -1696,6 +1697,7 @@
"description": "Enable Cloud Topic storage mode for this topic. When enabled, topic data is stored primarily in object storage with local storage used only as a write buffer.\n\nTIP: To configure storage modes with more flexibility, use <<redpandastorage-mode, `redpanda.storage.mode`>> which supports `local`, `tiered`, `cloud`, and `unset` modes.",
"related_topics": [
"self-managed-only: xref:develop:manage-topics/cloud-topics.adoc[Cloud Topics]",
"cloud-only: xref:develop:topics/cloud-topics.adoc[Cloud Topics]",
"self-managed-only: xref:manage:tiered-storage.adoc[Tiered Storage]"
],
"config_scope": "topic",
Expand Down Expand Up @@ -1954,6 +1956,10 @@
"config_scope": "broker",
"category": "redpanda"
},
"rpk_path": {
"description": "Path to RPK binary.",
"config_scope": "cluster"
},
"rps_limit_acls_and_users_operations": {
"description": "Rate limit, in requests per second, for ACL and user operations on the controller. The controller processes cluster management requests (such as creating, deleting, and updating ACLs and users) through the controller log (raft0).",
"config_scope": "cluster"
Expand All @@ -1974,10 +1980,6 @@
"description": "Rate limit, in requests per second, for topic operations on the controller. The controller processes cluster management requests (such as creating, deleting, and updating topics and partition counts) through the controller log (raft0).",
"config_scope": "cluster"
},
"rpk_path": {
"description": "Path to RPK binary.",
"config_scope": "cluster"
},
"sasl_mechanism": {
"description": "The SASL mechanism to use when the HTTP Proxy client connects to the Kafka API. These credentials are used when the HTTP Proxy API listener has <<http_proxy_auth_method, `authentication_method`>>: `none` but the cluster requires authenticated access to the Kafka API.\n\nThis property specifies which individual SASL mechanism the HTTP Proxy client should use, while the cluster-wide available mechanisms are configured using the xref:reference:properties/cluster-properties.adoc#sasl_mechanisms[`sasl_mechanisms`] cluster property.\n\ninclude::shared:partial$http-proxy-ephemeral-credentials-breaking-change.adoc[]\n\nNOTE: While the cluster-wide xref:reference:properties/cluster-properties.adoc#sasl_mechanisms[`sasl_mechanisms`] property may support additional mechanisms (PLAIN, GSSAPI, OAUTHBEARER), HTTP Proxy client connections only support SCRAM mechanisms.",
"related_topics": [
Expand Down Expand Up @@ -2251,7 +2253,7 @@
"write.caching": {
"description": "The write caching mode to apply to a topic.\n\nWhen `write.caching` is set, it overrides the cluster property xref:cluster-properties.adoc#write_caching_default[`write_caching_default`]. 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. Fsyncs follow <<flushms, `flush.ms`>> and <<flushbytes, `flush.bytes`>>, whichever is reached first.",
"related_topics": [
"xref:develop:config-topics.adoc#configure-write-caching[Write caching]",
"xref:develop:manage-topics/config-topics.adoc#configure-write-caching[Write caching]",
"xref:manage:tiered-storage.adoc[Tiered Storage]",
"xref:reference:properties/cluster-properties.adoc#write_caching_default[`write_caching_default`]",
"xref:cluster-properties.adoc#write_caching_default[`write_caching_default`]"
Expand All @@ -2261,7 +2263,7 @@
"write_caching_default": {
"related_topics": [
"xref:reference:properties/topic-properties.adoc#writecaching[`write.caching`]",
"xref:develop:config-topics.adoc#configure-write-caching[Write caching]"
"xref:develop:manage-topics/config-topics.adoc#configure-write-caching[Write caching]"
],
"config_scope": "cluster",
"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#writecaching[`write.caching`] topic property."
Expand Down
64 changes: 64 additions & 0 deletions docs-data/redpanda-property-changes-26.1.1-to-v26.1.1.json
Original file line number Diff line number Diff line change
@@ -0,0 +1,64 @@
{
"comparison": {
"oldVersion": "26.1.1",
"newVersion": "v26.1.1",
"timestamp": "2026-04-07T01:43:16.118Z"
},
"summary": {
"newProperties": 0,
"changedDefaults": 3,
"changedDescriptions": 1,
"changedTypes": 1,
"deprecatedProperties": 0,
"removedDeprecatedProperties": 0,
"removedProperties": 0,
"emptyDescriptions": 2
},
"details": {
"newProperties": [],
"changedDefaults": [
{
"name": "kafka_handler_latency_all",
"oldDefault": false,
"newDefault": null
},
{
"name": "max_concurrent_producer_ids",
"oldDefault": 100000,
"newDefault": "Maximum value"
},
{
"name": "max_transactions_per_coordinator",
"oldDefault": 10000,
"newDefault": "Maximum value"
}
],
"changedDescriptions": [
{
"name": "kafka_handler_latency_all",
"oldDescription": "Enable latency histograms for all Kafka API handlers. When disabled, only important handlers (produce, fetch, metadata, api_versions, offset_commit) have latency histograms.",
"newDescription": "Configuration property: kafka_handler_latency_all"
}
],
"changedTypes": [
{
"name": "kafka_handler_latency_all",
"oldType": "boolean",
"newType": "string"
}
],
"deprecatedProperties": [],
"removedDeprecatedProperties": [],
"removedProperties": [],
"emptyDescriptions": [
{
"name": "redpanda.remote.allowgaps",
"type": "boolean"
},
{
"name": "redpanda.virtual.cluster.id",
"type": "string"
}
]
}
}
Loading
Loading