This is an automated email from the ASF dual-hosted git repository.
chia7712 pushed a commit to branch 3.9
in repository https://gitbox.apache.org/repos/asf/kafka.git
The following commit(s) were added to refs/heads/3.9 by this push:
new 0b5b8c5a0d9 KAFKA-19026: amend note in KRaft migration docs (#21210)
0b5b8c5a0d9 is described below
commit 0b5b8c5a0d90b2bca0b478d59410ca23e7191d12
Author: Edoardo Comar <[email protected]>
AuthorDate: Wed Dec 24 07:19:22 2025 +0000
KAFKA-19026: amend note in KRaft migration docs (#21210)
mention the compatibility flag in the migration docs
Reviewers: Chia-Ping Tsai <[email protected]>
---
docs/getting-started/upgrade.md | 6 ++++++
docs/operations/kraft.md | 2 +-
2 files changed, 7 insertions(+), 1 deletion(-)
diff --git a/docs/getting-started/upgrade.md b/docs/getting-started/upgrade.md
index 92302a10ef4..d7347b3ee83 100644
--- a/docs/getting-started/upgrade.md
+++ b/docs/getting-started/upgrade.md
@@ -58,6 +58,12 @@ If you are upgrading from version 2.4.0 or above, and you
have not overridden th
+### Notable changes in 3.9.2
+
+ * There is a new server configuration,
`alter.config.policy.kraft.compatibility.enable`, which ensures that an
AlterConfigPolicy is invoked consistently between KRaft and ZooKeeper modes. To
enable this behavior, set the property to `true` in `server.properties`. For
backward compatibility, the default value is `false`. See
[KIP-1252](https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=399279475)
for more details.
+
+
+
### Notable changes in 3.9.1
* We have added a system property
("org.apache.kafka.sasl.oauthbearer.allowed.urls") to set the allowed URLs as
SASL OAUTHBEARER token or jwks endpoints. By default all URLs are allowed.
Users should explicitly set the desired allowed list if necessary.
diff --git a/docs/operations/kraft.md b/docs/operations/kraft.md
index e0159f8ad9a..4ce8474cb77 100644
--- a/docs/operations/kraft.md
+++ b/docs/operations/kraft.md
@@ -275,7 +275,7 @@ In general, the migration process passes through several
phases.
* After the migration has been finalized, it is not possible to revert back
to ZooKeeper mode.
* During the migration, if a ZK broker is running with multiple log
directories, any directory failure will cause the broker to shutdown. Brokers
with broken log directories will only be able to migrate to KRaft once the
directories are repaired. For further details refer to
[KAFKA-16431](https://issues.apache.org/jira/browse/KAFKA-16431).
* As noted above, some features are not fully implemented in KRaft mode. If
you are using one of those features, you will not be able to migrate to KRaft
yet.
- * There is a known inconsistency between ZK and KRaft modes in the arguments
passed to an `AlterConfigPolicy`, when an `OpType.SUBTRACT` is processed. For
further details refer to
[KAFKA-19026](https://issues.apache.org/jira/browse/KAFKA-19026).
+ * There is a known inconsistency between ZK and KRaft modes in the arguments
passed to an `AlterConfigPolicy`, when operations of type `SUBTRACT`, `DELETE`
or `APPEND` are processed. This has been addressed with a compatibility flag in
version 3.9.2. For further details see
[KIP-1252](https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=399279475).
