[KAFKA-362] Source Connector - Exactly Once Semantics (KIP-618) Created: 29/Mar/23 Updated: 27/Oct/23 Resolved: 20/Apr/23 |
|
| Status: | Closed |
| Project: | Kafka Connector |
| Component/s: | Sink |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | New Feature | Priority: | Major - P3 |
| Reporter: | Robin Fehr | Assignee: | Robert Walters |
| Resolution: | Gone away | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Description |
|
We're wondering if it would be feasible to implement the introduced properties by [KIP-618|https://cwiki.apache.org/confluence/display/KAFKA/KIP-618%3A+Exactly-Once+Support+for+Source+Connectors|https://cwiki.apache.org/confluence/display/KAFKA/KIP-618%3A+Exactly-Once+Support+for+Source+Connectors] that got deployed in Kafka 3.3. exactly.once.support transaction.boundary offsets.storage.topic transaction.boundary.interval.ms into the source connector or if that for some reason wouldn't work. |
| Comments |
| Comment by PM Bot [ 20/Apr/23 ] |
|
There hasn't been any recent activity on this ticket, so we're resolving it. Thanks for reaching out! Please feel free to comment on this if you're able to provide more information. |
| Comment by PM Bot [ 12/Apr/23 ] |
|
Hey robin.fehr@dormakaba.com, We need additional details to investigate the problem. If this is still an issue for you, please provide the requested information. |
| Comment by Robin Fehr [ 04/Apr/23 ] |
|
we currently use it in a use case where we write to a MongoDB collection in an append only fashion. (e.g. logs / event-stores etc.) |
| Comment by Robert Walters [ 04/Apr/23 ] |
|
robin.fehr@dormakaba.com Can you provide your use case where you would need exactly once ? Would this be for a Mongo to Mongo replication scenario or ? |