You are viewing a plain text version of this content. The canonical link for it is here.

Posted to jira@kafka.apache.org by "Lorcan (Jira)" <ji...@apache.org> on 2025/10/02 15:14:00 UTC

[jira] [Assigned] (KAFKA-16616) refactor mergeWith in MetadataSnapshot

     [ https://issues.apache.org/jira/browse/KAFKA-16616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Lorcan reassigned KAFKA-16616:
------------------------------

    Assignee:     (was: Lorcan)

> refactor mergeWith in MetadataSnapshot
> --------------------------------------
>
>                 Key: KAFKA-16616
>                 URL: https://issues.apache.org/jira/browse/KAFKA-16616
>             Project: Kafka
>          Issue Type: Improvement
>    Affects Versions: 3.7.0
>            Reporter: Alyssa Huang
>            Priority: Minor
>
> Right now we keep track of topic ids and partition metadata to add/update separately in mergeWith (e.g. two maps passed as arguments). This means we iterate over topic metadata twice which could be costly when we're dealing with a large number of updates. 
> `updatePartitionLeadership` which calls `mergeWith` does something similarly (generates map of topic ids to update in a loop separate from the list of partition metadata to update) and should be refactored as well.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)