...

A better solution is to store config registrations in an internal topic and perform ad hoc aggregations on registrations for a particular entity to gather compatibility information about clients that are tied to that entity. For example, all versions of clients that registered with an entity along with the supported configs for each version of client could be aggregated and returned to the user in the DescribeClientConfigsResponse. The . The Java producer and consumer clients can register the configs they they support with a DescribeClientConfigsRequest. The broker can write a key-value pair to an internal topic if it receives a DescribeClientConfigsRequest where upon receiving the request where the key is the <user, client-id> entity and the value is ClientVersion along with the list of supported configs. A key does not need to be written if the client provided a null SupportedConfigs list.

Ad hoc aggregations of registrations for a particular entity could be performed to give descriptive information about client config compatibility to the user. For example, all versions of clients that registered with an entity along with the supported configs for each version of client could be aggregated and returned to the user in the DescribeClientConfigsResponse. 

Public Interfaces

...

Admin Client Changes

...