You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Apoorv Mittal (Jira)" <ji...@apache.org> on 2026/09/10 15:15:00 UTC

[jira] [Commented] (KAFKA-19441) Encapsulate MetadataImage in GroupCoordinator

    [ https://issues.apache.org/jira/browse/KAFKA-19441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18113906#comment-18113906 ] 

Apoorv Mittal commented on KAFKA-19441:
---------------------------------------

[~dajac] seems the PR is merged, shall I resolve the issue?

> Encapsulate MetadataImage in GroupCoordinator
> ---------------------------------------------
>
>                 Key: KAFKA-19441
>                 URL: https://issues.apache.org/jira/browse/KAFKA-19441
>             Project: Kafka
>          Issue Type: Improvement
>          Components: group-coordinator
>    Affects Versions: 4.0.0
>            Reporter: Liz Bennett
>            Assignee: Liz Bennett
>            Priority: Major
>
> The MetadataImage has a ton of stuff in it and it gets passed around all over the place in the new GroupCoordinator. This makes it difficult to understand what metadata the group coordinator actually relies on and makes it too easy to use metadata in ways it wasn't meant to be used. 
>  
> If we encapsulate the MetadataImage in an interface that clearly indicates what metadata the group coordinator actually uses, it is much easier at a glance to see what dependencies it has on the metadata. Also, if the source of metadata needs to evolve for whatever reason, we can do so easily by wrapping MetadataImage in an interface.



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