[jira] [Resolved] (KAFKA-7567) Clean up internal metadata usage for consistency and extensibility

["Jason Gustafson (JIRA)" <ji...@apache.org>]

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

Jason Gustafson resolved KAFKA-7567.
------------------------------------
       Resolution: Fixed
    Fix Version/s: 2.2.0

> Clean up internal metadata usage for consistency and extensibility
> ------------------------------------------------------------------
>
>                 Key: KAFKA-7567
>                 URL: https://issues.apache.org/jira/browse/KAFKA-7567
>             Project: Kafka
>          Issue Type: Improvement
>            Reporter: Jason Gustafson
>            Assignee: Jason Gustafson
>            Priority: Major
>             Fix For: 2.2.0
>
>
> This refactor has two objectives to improve metadata handling logic and testing:
> 1. We want to reduce dependence on the public object `Cluster` for internal metadata propagation since it is not easy to evolve. As an example, we need to propagate leader epochs from the metadata response to `Metadata`, but it is not straightforward to do this without exposing it in `PartitionInfo` since that is what `Cluster` uses internally. By doing this change, we are able to remove some redundant `Cluster` building logic. 
> 2. We want to make the metadata handling in `MockClient` simpler and more consistent. Currently we have mix of metadata update mechanisms which are internally inconsistent with each other and also do not match the implementation in `NetworkClient`.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)