Thanks everyone who has voted so far! Jun brought up a good point offline that the BeginTxnRequest was not strictly needed since there is no state to recover until a partition has been added to the transaction. Instead we can start the transaction implicitly upon receiving the first AddPartitionsToTxn request. This results in a slight change of behavior since the transaction timeout will be enforced only after the first send() instead of the beginTransaction(). However, the main point of the timeout is to avoid blocking downstream consumers, which is only possible once you've added a partition to the transaction, so we feel the simplification is justified. I've updated the document accordingly.
Thanks, Jason On Tue, Feb 14, 2017 at 2:03 PM, Jay Kreps <j...@confluent.io> wrote: > +1 > > Super happy with how this turned out. It's been a long journey since we > started thinking about this 3+ years ago. Can't wait to see it in > code---this is a big one! :-) > > -Jay > > On Wed, Feb 1, 2017 at 8:13 PM, Guozhang Wang <wangg...@gmail.com> wrote: > > > Hi all, > > > > We would like to start the voting process for KIP-98. The KIP can be > found > > at > > > > https://cwiki.apache.org/confluence/display/KAFKA/KIP- > > 98+-+Exactly+Once+Delivery+and+Transactional+Messaging > > > > Discussion thread can be found here: > > > > http://search-hadoop.com/m/Kafka/uyzND1jwZrr7HRHf?subj=+ > > DISCUSS+KIP+98+Exactly+Once+Delivery+and+Transactional+Messaging > > > > Thanks, > > > > -- > > -- Guozhang > > >
