[
https://issues.apache.org/jira/browse/KAFKA-19026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17947225#comment-17947225
]
Luke Chen commented on KAFKA-19026:
-----------------------------------
Thanks for the explanation!
>From what I can see, this behavior in ZK has been existed for a long time (I
>also tested in 3.6.0 and has the same result) and the KRaft behavior works as
>expected, do you think this change will "break the backward compatibility" in
>ZK mode if users want to stay in ZK in 3.9.x release?
Maybe we can consider to document the inconsistent behavior in [ZooKeeper to
KRaft Migration|https://kafka.apache.org/documentation/#kraft_zk_migration]
section in 3.9 to notify users who plan to migrate from ZK to KRaft to resolve
this issue?
> AlterConfigPolicy incompatibility between ZK mode and KRaft mode when using
> AlterConfigOp.OpType.SUBTRACT/APPEND
> ----------------------------------------------------------------------------------------------------------------
>
> Key: KAFKA-19026
> URL: https://issues.apache.org/jira/browse/KAFKA-19026
> Project: Kafka
> Issue Type: Bug
> Components: core, migration
> Affects Versions: 3.9.0, 3.8.1
> Reporter: Edoardo Comar
> Assignee: Edoardo Comar
> Priority: Major
> Fix For: 3.9.2
>
> Attachments: KAFKA19026Policy.java, KAFKA19026Test.java
>
>
> When processing an Incremental Alter Config on a Config entry of type List
> with OpType.SUBTRACT
> the metadata passed to {color:#000000}AlterConfigPolicy.validate contains
> {color}
> * {color:#000000}in KRaft mode : {color}{color:#000000}the config that would
> result AFTER the subtraction{color}
> * {color:#000000}in ZK mode : the config as if the opType was OpType.SET,
> with no indication that actually the value would be removed{color}
> {color:#000000}Also OpType.APPEND behaves inconsistently in this regard{color}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
