Makes sense to allow users to comply with their requirements without taking on the maintenance cost of keeping up with new headers across different versions. Thanks for the KIP Jeff.
+1 (binding) Konstantine On Tue, May 12, 2020 at 3:13 AM Manikumar <manikumar.re...@gmail.com> wrote: > +1 (binding) > > Thanks for the KIP. > > On Wed, May 6, 2020 at 7:57 PM Randall Hauch <rha...@gmail.com> wrote: > > > Thanks for putting this together. > > > > +1 (binding) > > > > On Fri, Apr 17, 2020 at 2:02 PM Aneel Nazareth <an...@confluent.io> > wrote: > > > > > Thanks Jeff, this seems like it addresses a user need. > > > > > > +1 (non-binding) > > > > > > On Fri, Apr 17, 2020 at 1:28 PM Zhiguo Huang <jeff.hu...@confluent.io> > > > wrote: > > > > > > > > Thanks to everyone for their input. I've incorporated the changes, > and > > I > > > > think this is ready for voting. > > > > > > > > To summarize, the KIP simply proposes to add a feature which allows > > HTTP > > > > response headers configured for Kafka Connect.The KIP can be found > > here: > > > > > > > > > > https://cwiki.apache.org/confluence/display/KAFKA/KIP+577%3A+Allow+HTTP+Response+Headers+to+be+Configured+for+Kafka+Connect > > > > > > > > Thanks! > > > > > > > > Jeff. > > > > > >
