Thanks everyone! I'm going to close the vote.

Martijn Visser +1
Justine Olshan +1 (binding)
Omnia Ibrahim +1
Jason Gustafson +1 (binding)
Jun Rao +1 (binding)

The KIP is accepted.

-Artem

On Mon, Jul 22, 2024 at 10:57 AM Jun Rao <j...@confluent.io.invalid> wrote:

> Hi, Artem,
>
> Thanks for the KIP. +1 from me.
>
> Jun
>
> On Wed, May 29, 2024 at 9:41 AM Jason Gustafson <ja...@confluent.io.invalid
> >
> wrote:
>
> > +1 Thanks for the KIP!
> >
> > On Wed, Mar 13, 2024 at 5:13 AM Omnia Ibrahim <o.g.h.ibra...@gmail.com>
> > wrote:
> >
> > > I had a look at the discussion thread and the KIP looks exciting.
> > > +1 non-binding
> > >
> > > Best
> > > Omnia
> > >
> > > On 1 Dec 2023, at 19:06, Artem Livshits <alivsh...@confluent.io
> .INVALID>
> > > wrote:
> > >
> > > Hello,
> > >
> > > This is a voting thread for
> > >
> > >
> >
> https://cwiki.apache.org/confluence/display/KAFKA/KIP-939%3A+Support+Participation+in+2PC
> > > .
> > >
> > > The KIP proposes extending Kafka transaction support (that already uses
> > 2PC
> > > under the hood) to enable atomicity of dual writes to Kafka and an
> > external
> > > database, and helps to fix a long standing Flink issue.
> > >
> > > An example of code that uses the dual write recipe with JDBC and should
> > > work for most SQL databases is here
> > > https://github.com/apache/kafka/pull/14231.
> > >
> > > The FLIP for the sister fix in Flink is here
> > >
> >
> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=255071710
> > >
> > > -Artem
> > >
> >
>

Reply via email to