Hi Alex, I think WADL support was likely unintentional, so this could be treated as more of a bug. Unless we think it's a good idea to support it going forward, I'd suggest going with the rejected alternative of just turning it off. What do you think?
Thanks, Jason On Fri, Dec 14, 2018 at 3:06 PM Oleksandr Diachenko < alex.diache...@confluent.io> wrote: > Thanks, everyone for taking the time to review the KIP. > > It looks like there are no major objections on it, so I will start voting > thread. > > Regards, Alex. > > > > On Thu, Dec 13, 2018 at 3:50 PM Randall Hauch <rha...@gmail.com> wrote: > > > Thanks, Alex. The KIP looks good to me. > > > > Randall > > > > On Wed, Dec 12, 2018 at 10:08 PM Guozhang Wang <wangg...@gmail.com> > wrote: > > > > > Alex, > > > > > > Thanks for putting up this KIP. The proposal lgtm. > > > > > > Guozhang > > > > > > On Wed, Dec 12, 2018 at 7:41 PM Oleksandr Diachenko < > > odiache...@apache.org > > > > > > > wrote: > > > > > > > Hi all, > > > > > > > > I would like to start a discussing for the following KIP: > > > > > > > > > > > > > > https://cwiki.apache.org/confluence/display/KAFKA/KIP-404%3A+Add+Kafka+Connect+configuration+parameter+for+disabling+WADL+output+on+OPTIONS+request > > > > . > > > > > > > > The KIP proposes to add a configuration parameter for Connect Worker, > > > which > > > > would allow to not expose WADL information in Connect REST api > > responces. > > > > > > > > Feedback is appreciated, thanks in advance. > > > > > > > > Regards, Alex. > > > > > > > > > > > > > -- > > > -- Guozhang > > > > > >
