Question: Is there a plan for transactions for the producer?
See original GitHub issueIs there a plan for a transactions for the producer?
Something like the following:
producer.beginTransaction();
for (ConsumerRecord record : records)
producer.send(producerRecord(“outputTopic”, record));
producer.sendOffsetsToTransaction(currentOffsets(consumer), group);
producer.commitTransaction();
Referenced from: https://www.confluent.io/blog/transactions-apache-kafka/
We are in need of this, and we are seeing if we should do a quick workaround or if we should wait. Unless someone can guide us on what that could look like, we might be able to contribute.
Issue Analytics
- State:
- Created 4 years ago
- Reactions:2
- Comments:15 (8 by maintainers)
Top Results From Across the Web
The Questions Every Entrepreneur Must Answer
After defining or redefining the business and verifying its basic soundness, an entrepreneur should determine whether plans for its growth are appropriate.
Read more >275-1 SUITABILITY IN ANNUITY TRANSACTIONS MODEL ...
“Replacement” means a transaction in which a new annuity is to be purchased, and it is known or should be known to the...
Read more >How to manage Kafka transactional producer objects in ...
Long answer. As the docs say, transactional producers are not thread safe. As is hinted at in the example, there can be only...
Read more >KIP-447: Producer scalability for exactly once semantics
Essentially this allows us to guarantee that for a given transactional Id, there can only be one producer instance that is active and...
Read more >Exactly-Once Semantics Are Possible: Here's How Kafka ...
In this post, I'd like to tell you what Kafka's exactly-once semantics mean, why it is a hard problem, and how the new...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@noahdav The implementation is pretty much complete and we have full transactional functionality. We’re currently working on writing tests, there’s a lot of intricate error cases that needs proper handling.
We really do appreciate your help; I believe the most valuable thing right now is testing, in particular to cover real world use-cases. So my suggestion would be for you to start using the new transactional API in your applications and report back any issues you may find.
The
txns
branch is not yet ready for wider use but it will be cleaned up this week and should be ready to go by next monday.@edenhill please let us know when we can start testing with this branch.