You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Jason Gustafson (JIRA)" <ji...@apache.org> on 2018/10/29 23:10:00 UTC

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

Jason Gustafson created KAFKA-7567:
--------------------------------------

             Summary: 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


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)