[
https://issues.apache.org/jira/browse/KAFKA-18398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17910328#comment-17910328
]
Matthias J. Sax commented on KAFKA-18398:
-----------------------------------------
I think there is two things:
* Is there any actually _invalid_ configs, which we should disallow? For this
case, we should maybe log a WARN (or even fail)?
* If there is diff between code and configs, but it's a totally valid config,
we should not log but just apply the config to the topic, and thus address
K7803. (Of course, the side effect will be, that if somebody changes a topic
config "in the background", KS code would overwrite it – but I guess that is
desired?)
I am open to other suggestions of course.
The main point of linking both tickets was, that given the current setup,
people might change topic config in the background w/o updating the code. Thus
could lead to many spurious WARN logs if we start to compare code and topic
config and log a WARN for everything we do not expect.
> Log a warning if actual topic configs are inconsistent with the required
> topic configs
> --------------------------------------------------------------------------------------
>
> Key: KAFKA-18398
> URL: https://issues.apache.org/jira/browse/KAFKA-18398
> Project: Kafka
> Issue Type: Sub-task
> Reporter: Lucas Brutschy
> Assignee: Alieh Saeedi
> Priority: Major
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
