+1 (binding)

Thanks for the KIP, Cheng!

On Tue, Dec 8, 2020 at 12:23 AM Ismael Juma <ism...@juma.me.uk> wrote:

> Thanks, +1 (binding).
>
> On Mon, Dec 7, 2020 at 1:40 PM Cheng Tan <c...@confluent.io> wrote:
>
> > Hi Ismael,
> >
> > Yes. Add deprecation warning for `IDEMPOTENT_WRITE` in 3.0 makes sense.
> > I’ve updated the KIP’s “DEMPOTENT_WRITE Deprecation” section to reflect
> > your suggestion. Please let me know if you have more suggestions. Thanks.
> >
> >
> > Best, - Cheng Tan
> >
> >
> > > On Dec 7, 2020, at 6:42 AM, Ismael Juma <ism...@juma.me.uk> wrote:
> > >
> > > Thanks for the KIP Cheng. One suggestion: should we add the
> `kafka-acls`
> > > deprecation warnings for `IDEMPOTENT_WRITE` in 3.0? That would give
> time
> > > for authorizer implementations to be updated.
> > >
> > > Ismael
> > >
> > > On Fri, Dec 4, 2020 at 11:00 AM Cheng Tan <c...@confluent.io <mailto:
> > c...@confluent.io>> wrote:
> > >
> > >> Hi all,
> > >>
> > >> I’m proposing a new KIP for enabling the strongest delivery guarantee
> by
> > >> default. Today Kafka support EOS and N-1 concurrent failure tolerance
> > but
> > >> the default settings haven’t bring them out of the box. The proposal
> > >> changes include the producer defaults change to `ack=all` and
> > >> `enable.idempotence=true`. Also, the ACL operation type
> > IDEMPOTENCE_WRITE
> > >> will be deprecated. If a producer has WRITE permission to any topic,
> it
> > >> will be able to request a producer id and perform idempotent produce.
> > >>
> > >> KIP here:
> > >>
> > >>
> >
> https://cwiki.apache.org/confluence/display/KAFKA/KIP-679%3A+Producer+will+enable+the+strongest+delivery+guarantee+by+default
> > >> <
> > >>
> >
> https://cwiki.apache.org/confluence/display/KAFKA/KIP-679:+Producer+will+enable+the+strongest+delivery+guarantee+by+default
> > <
> >
> https://cwiki.apache.org/confluence/display/KAFKA/KIP-679:+Producer+will+enable+the+strongest+delivery+guarantee+by+default
> > >
> > >>>
> > >>
> > >> Please vote in this mail thread.
> > >>
> > >> Thanks
> > >>
> > >> - Cheng Tan
> >
> >
>

Reply via email to