[
https://issues.apache.org/jira/browse/KAFKA-16212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17817795#comment-17817795
]
Justine Olshan commented on KAFKA-16212:
----------------------------------------
Thanks [~omnia_h_ibrahim] I remember this particularly being a tricky area for
topic IDs, so I appreciate the time being spent here.
For fetch requests, I remember we had to do something similar to proposal 1 for
the fetch path. When we receive fetch request < 13, we will have a zero topic
ID stored. (Note – this is a placeholder and can not be used as a valid topic
ID)
Does using the zero uuid make some of option 1 easier? Or are we already using
the zero uuid to signify something?
> Cache partitions by TopicIdPartition instead of TopicPartition
> --------------------------------------------------------------
>
> Key: KAFKA-16212
> URL: https://issues.apache.org/jira/browse/KAFKA-16212
> Project: Kafka
> Issue Type: Improvement
> Affects Versions: 3.7.0
> Reporter: Gaurav Narula
> Assignee: Omnia Ibrahim
> Priority: Major
>
> From the discussion in [PR
> 15263|https://github.com/apache/kafka/pull/15263#discussion_r1471075201], it
> would be better to cache {{allPartitions}} by {{TopicIdPartition}} instead of
> {{TopicPartition}} to avoid ambiguity.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
