[KAFKA-312] Support tombstone events for deletes when using fullDocumentOnly. Created: 05/May/22 Updated: 28/Oct/23 Resolved: 15/Dec/22 |
|
| Status: | Closed |
| Project: | Kafka Connector |
| Component/s: | Source |
| Affects Version/s: | None |
| Fix Version/s: | 1.9.0 |
| Type: | New Feature | Priority: | Unknown |
| Reporter: | Ross Lawley | Assignee: | Ross Lawley |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Quarter: | FY23Q4 | ||||||||
| Case: | (copied to CRM) | ||||||||
| Documentation Changes: | Needed | ||||||||
| Documentation Changes Summary: | When using fullDocument (not the change stream) to kafka, and in case of a delete operation a tombstone (a message with null value and non-null key) is sent to notify consumers of data deletion. Add new configuration: publish.full.document.only.tombstone.on.delete - defaults to false. Send a null value on a delete event. Requires publish.full.document.only=true. |
||||||||
| Description |
|
Add publish.full.document.only.tombstone.on.delete PR: https://github.com/mongodb/mongo-kafka/pull/105 Similar to the Debezium `tombstones.on.delete` feature. When using fullDocument (not the change stream) to kafka, and in case of a delete operation a tombstone (a message with null value and non-null key) is sent to notify consumers of data deletion. |
| Comments |
| Comment by Ross Lawley [ 15/Dec/22 ] |
|
Rebased and merged the users PR. *Note: *I renamed the configuration option to: publish.full.document.only.tombstone.on.delete to be super explicit and to follow the convention in relating the configuration to the higher level config (publish.full.document.only). |
| Comment by Githook User [ 15/Dec/22 ] |
|
Author: {'name': 'Cosimo Meli', 'email': 'cosimo.meli@chili.com'}Message: Added publish.full.document.only.tombstone.on.delete Supports producing tombstones for deletions when
|