[
https://issues.apache.org/jira/browse/KAFKA-13612?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17481500#comment-17481500
]
Luke Chen commented on KAFKA-13612:
-----------------------------------
[~hachikuji] , I agree with [~dnwe] , we can work well without patching this
issue, of course. But I think the internal topics should be available as early
as possible to ensure the following requests queryable.
[~cmccabe] , I agree we don't guarantee anything about their format or whether
or not they are present, etc, so this is not a regression issue. But I think
this should be a good improvement to create the internal topics when
metadataRequest received, like before, to have the internal topics ready as
early as possible.
What do you think?
> internal topics won't be created in metadataRequest when
> auto.create.topics.enable=false
> ----------------------------------------------------------------------------------------
>
> Key: KAFKA-13612
> URL: https://issues.apache.org/jira/browse/KAFKA-13612
> Project: Kafka
> Issue Type: Bug
> Affects Versions: 2.8.0, 3.0.0
> Reporter: Luke Chen
> Assignee: Luke Chen
> Priority: Major
>
> In KAFKA-9751, when create internal topics through FindCoordinator or
> Metadata request, we route the topic creation request to the controller
> instead of handling by itself. We change logic in
> `KafkaApis#getTopicMetadata`, and make the internal topic won't get created
> when "auto.create.topics.enable=false`.
> h4.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
