Yeah, I agree... having a validation mode would be nice.  We should be
explicit that passing validation doesn't 100% guarantee that a
subsequent call to create the topic will succeed, though.  There is an
obvious race condition there-- for example, with a plugin which consults
some external authentication system, there could be a change to the
privileges in between validation and attempted creation.

It also seems like we should try to provide a helpful exception message
for the cases where topic creation fails.  This might involve adding
more detail about error conditions to CreateTopicsRequest... right now
it just returns an error code, but a text message would be a nice
addition.

cheers,
Colin


On Thu, Jan 5, 2017, at 13:41, dan wrote:
> it would be nice to have a dry-run or validate ability added to this kip.
> since we are offloading validation to a 3rd party implementor a random
> user
> can't know a priori (based solely on kafka configs) whether a call should
> succeed without actually creating the topic.
> 
> a similar case is in connect where there is a separate endpoint
> <https://github.com/apache/kafka/blob/trunk/connect/runtime/src/main/java/org/apache/kafka/connect/runtime/rest/resources/ConnectorPluginsResource.java#L49-L58>
> to attempt to validate a connect configuration without actually creating
> the connector.
> 
> thanks
> dan
> 
> 
> On Thu, Jan 5, 2017 at 7:34 AM, Ismael Juma <ism...@juma.me.uk> wrote:
> 
> > Hi all,
> >
> > We've posted "KIP-108: Create Topic Policy" for discussion:
> >
> > https://cwiki.apache.org/confluence/display/KAFKA/KIP-
> > 108%3A+Create+Topic+Policy
> >
> > Please take a look. Your feedback is appreciated.
> >
> > Thanks,
> > Ismael
> >

Reply via email to