Hi Shailesh, I think most users of the DescribeConfigs API do not want to get help text or configuration schema information. So, it would be inefficient to always include this information as part of the DescribeConfigs response. It would be better to create a new, separate API for getting this configuration schema information, if that's what we really want. This API should probably also allow configuration management systems to list all the possible configurations for topics, brokers, etc., which is something that I think many of them would want.
We also need to consider compatibility. One example is, what if we later add a new type of configuration key, such as UUID. What would the hypothetical DescribeConfigurationSchema API return in this case, for older clients? We probably need an UNKNOWN enum value to be used to indicate that the server knows about configuration key types that the client does not. best, Colin On Wed, Feb 19, 2020, at 09:13, Shailesh Panwar wrote: > Bump. > > Thanks > Shailesh > > On Tue, Feb 11, 2020 at 1:00 PM Shailesh Panwar <span...@confluent.io> > wrote: > > > Hi all, > > We would like to extend the DescribeConfigsResponse schema to include the > > data-type of the fields. > > > > The KIP can be found here: > > > > https://cwiki.apache.org/confluence/display/KAFKA/KIP-569%3A+DescribeConfigsResponse+-+Update+the+schema+to+include+datatype+of+the+field > > > > Thanks > > Shailesh > > >
