[
https://issues.apache.org/jira/browse/KAFKA-14764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17694076#comment-17694076
]
David Jacot commented on KAFKA-14764:
-------------------------------------
[~dengziming] If I remember correctly, you did the implementation. Could you
double check this?
> Metadata API ignores topic names if at least one topic is provided with an id
> -----------------------------------------------------------------------------
>
> Key: KAFKA-14764
> URL: https://issues.apache.org/jira/browse/KAFKA-14764
> Project: Kafka
> Issue Type: Bug
> Reporter: David Jacot
> Priority: Major
>
> The Metadata API accepts both topic names and topic ids in the request. This
> suggests that a single request could mix them in. At least, we have no logic
> on the server side to prevent this. The issue is that the server just ignores
> any topic specified with a name if there is at least one topic specified with
> an id in the request. In other words, if a request contains topic-id-1,
> topic-id-2, topic-name-1 and topic-name-2, the response will only have
> metadata for topic-id-1 and topic-id-2.
> This does not hurt us today because the clients does not use topic ids in the
> request at all.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
