Hi Colin, Thanks for your feedback.
That is correct. I mention this in the future work section. I thought that we could remove it when we could also remove TopicAuthorizedOperations in order to remain consistent in the API. We can also do it immediately. I don't have a strong preference for any ways. What do you think? Best, David On Fri, Dec 18, 2020 at 1:51 PM David Jacot <dja...@confluent.io> wrote: > Hi Ryan, > > Thanks for your feedback. That's an interesting idea but that raises more > questions. At the moment, `describeCluster` only requires to be > authenticated > (if authentication is enabled) to get the basic information about the > cluster. > If we add the JMX port, is it something that we would provide without > requiring > more permissions? I am not sure about this. > > I lean towards keeping this KIP focused on introducing the new API and to > add new information with separate KIPs. There might be more information > that we want to add as part of KIP-500. > > I will be happy to hear what other members of the community think about > this. > > Best, > David > > On Thu, Dec 17, 2020 at 5:57 AM Colin McCabe <cmcc...@apache.org> wrote: > >> Hi David, >> >> This seems reasonable. It would be nice to have an API specifically for >> describeCluster, so that we could extend this API without adding more >> fields to the already large MetadataRequest. >> >> As you mention in the KIP, KIP-700 would allow us to deprecate >> MetadataRequest#ClusterAuthorizedOperations. So it seems like this KIP >> should specify a new version of MetadataRequest where the related fields >> are absent, right? >> >> best, >> Colin >> >> >> On Mon, Dec 14, 2020, at 08:10, David Jacot wrote: >> > Hi all, >> > >> > I'd like to propose a small KIP: >> > >> https://cwiki.apache.org/confluence/display/KAFKA/KIP-700%3A+Add+Describe+Cluster+API >> > >> > Please let me know what you think. >> > >> > Best, >> > David >> > >> >
