...
MetadataRequest must also be modified. Topic name will be left in to allow requests to be made either by topic name or topic ID. Requests should only use one or the other.
ID will be checked first, but if the value is the default zero UUID, topic name will be used instead. If an ID is specified and the ID does not exist, the request will fail regardless of allow_auto_topic_creation.
If the topic ID is not found, the request will return an UNKNOWN_TOPIC_ID
error indicating the topic ID did not exist. The check for the topic ID will occur before checking authorization on the topic. Thus, existence of a given topic ID is not considered sensitive information. If name and ID are included, but the name does not match the ID, the request will also fail with an UNKNOWN_TOPIC_ID
error.
MetadataRequest v10
|
...
Like the MetadataRequst, ID will be checked first, but if the value is the default zero UUID, topic name will be used instead. If an ID is specified and the ID does not exist, the request will fail.
If name and ID are included, but the name does not match the ID, the request will also fail.
DeleteTopicsResponse v6
|
Even in the cases where Although only topic ID or only topic name are included in the request, if topic Ids are supported, the response will contain both the name and the ID.
...