[
https://issues.apache.org/jira/browse/KAFKA-16212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17819023#comment-17819023
]
Justine Olshan commented on KAFKA-16212:
----------------------------------------
We use something similar in the fetch session cache when the topic ID is
unknown.
This transition state will be as long as we support ZK I would suspect.
> how would this look like that I need to be aware off during extending
> ReplicaManager cache to be topicId aware
Not sure I understand this question.
> 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)
