[
https://issues.apache.org/jira/browse/KAFKA-16212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17840715#comment-17840715
]
Omnia Ibrahim commented on KAFKA-16212:
---------------------------------------
I believe that https://issues.apache.org/jira/browse/KAFKA-10551 (and possibly
KAFKA-10549) needs to be done first as ProoduceRequest and Respond interact
with replicaManager cache to append log and it would be easier if this produce
request path is already topic ID aware before updating the cache. I am
prioritising KAFKA-10551
> 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)
