You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Colin McCabe (Jira)" <ji...@apache.org> on 2021/12/06 00:35:00 UTC
[jira] [Resolved] (KAFKA-13490) Fix some problems with KRaft createTopics and incrementalAlterConfigs
[ https://issues.apache.org/jira/browse/KAFKA-13490?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Colin McCabe resolved KAFKA-13490.
----------------------------------
Resolution: Fixed
> Fix some problems with KRaft createTopics and incrementalAlterConfigs
> ---------------------------------------------------------------------
>
> Key: KAFKA-13490
> URL: https://issues.apache.org/jira/browse/KAFKA-13490
> Project: Kafka
> Issue Type: Bug
> Affects Versions: 3.0.0
> Reporter: Colin McCabe
> Assignee: Colin McCabe
> Priority: Blocker
> Labels: kip-500
> Fix For: 3.1.0
>
>
> For CreateTopics, fix a bug where if one createTopics in a batch failed, they would all fail with the same error code. Make the error message for TOPIC_ALREADY_EXISTS consistent with the ZK-based code by including the topic name.
> For IncrementalAlterConfigs, before we allow topic configurations to be set, we should check that they are valid. (This also applies to newly created topics.) IncrementalAlterConfigs should ignore non-null payloads for DELETE operations. Previously we would return an error in these cases. However, this is not compatible with the old ZK-based code, which ignores the payload in these cases.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)