Quick update, I renamed ListAcls to DescribeAcls (and related classes and methods) as that is more consistent with other protocols (like ListGroups and DescribeGroups).
Ismael On Mon, May 8, 2017 at 2:17 PM, Ismael Juma <ism...@juma.me.uk> wrote: > Hi James, > > Yes, we will have a place where we perform validation independently of the > policy. This will be quite basic in the initial version, but we can improve > it over time. We will be able to do better than `ConfigCommand` because we > will have access to the broker topic configs. Without access to the broker > topic configs, not much could be validated by `ConfigCommand` (see > https://issues.apache.org/jira/browse/KAFKA-4788, for example). > > Ismael > > On Mon, May 8, 2017 at 5:39 AM, James Cheng <wushuja...@gmail.com> wrote: > >> The KIP talks about allowing the user to provide a AlterConfigsPolicy. I >> assume that even if the user does not provide a custom policy, that there >> are some basic validation that the broker will do by default? >> >> The reason I'm asking is I'm thinking ahead to >> https://issues.apache.org/jira/browse/KAFKA-4680, and wanted to know if >> there is going to be central place where we can do checks for stuff like >> that. >> >> -James >> >> > On May 4, 2017, at 10:32 PM, Ismael Juma <ism...@juma.me.uk> wrote: >> > >> > Hi all, >> > >> > We've posted "KIP-133: List and Alter Configs Admin APIs" for >> discussion: >> > >> > https://cwiki.apache.org/confluence/display/KAFKA/KIP-133% >> 3A+List+and+Alter+Configs+Admin+APIs >> > >> > This completes the first batch of AdminClient APIs so that topic, config >> > and ACL management is supported. >> > >> > Please take a look. Your feedback is appreciated. >> > >> > Thanks, >> > Ismael >> >> >
