[
https://issues.apache.org/jira/browse/KAFKA-19028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18111099#comment-18111099
]
Edoardo Comar commented on KAFKA-19028:
---------------------------------------
thanks [~crux]
getting a map with an entry key and null value on topic config delete seems
good.
When I opened the issue, I saw a missing entry even if the property was set
before deletion. This may have changed
> AlterConfigPolicy with OpType.DELETE : inconsistent behavior between TOPIC
> and BROKER resource
> ----------------------------------------------------------------------------------------------
>
> Key: KAFKA-19028
> URL: https://issues.apache.org/jira/browse/KAFKA-19028
> Project: Kafka
> Issue Type: Bug
> Reporter: Edoardo Comar
> Assignee: Arnab Nandy
> Priority: Major
>
> During an IncrementalAlterConfig that DELETES a config entry, the configs map
> that an AlterConfigPolicy will inspect appears to be inconsistent between the
> deletion of a broker property and the deletion of a topic property :
> when deleting a Topic property, the config entry is missing from the Map
> passed to the policy
> when deleting a Broker property, the config entry is present in the Map
> passed to the policy but the associated value is null.
> For consistency with the case of an OpType.SUBTRACT (which limited to a
> config entry of type List) the Map could instead contain the default value of
> the deleted property, if it exists.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
