[
https://issues.apache.org/jira/browse/KAFKA-7861?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16750034#comment-16750034
]
Edoardo Comar commented on KAFKA-7861:
--------------------------------------
Running the attached AlterConfigJira example, the output will show
{{Topic mytopic created}}
...
{{ConfigEntry(name=cleanup.policy, value=delete, source=DYNAMIC_TOPIC_CONFIG,
...}}
...
{{Altering Config ConfigResource}}
...
{{ConfigEntry(name=cleanup.policy, value=delete, source=DEFAULT_CONFIG}}
> AlterConfig may change the source of another config entry if it matches the
> broker default
> ------------------------------------------------------------------------------------------
>
> Key: KAFKA-7861
> URL: https://issues.apache.org/jira/browse/KAFKA-7861
> Project: Kafka
> Issue Type: Bug
> Components: core
> Affects Versions: 2.1.0
> Reporter: Edoardo Comar
> Priority: Major
> Attachments: AlterConfigJira.java
>
>
> * Create a topic with an explicit config entry that matches the broker's
> default (e.g. '"cleanup.policy"="delete");
> * Describe config - the entry will be of type DYNAMIC_TOPIC_CONFIG.
> * Alter some other config for the topic (e.g `segment.bytes`)
> * Describe config again - the previously DYNAMIC_TOPIC_CONFIG entry
> ("cleanup.policy") will be now described as DEFAULT_CONFIG.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
