[KAFKA-320] Support setting a custom delete writemodel strategy Created: 19/Jul/22 Updated: 08/Jan/24 Resolved: 01/May/23 |
|
| Status: | Closed |
| Project: | Kafka Connector |
| Component/s: | Sink |
| Affects Version/s: | None |
| Fix Version/s: | 1.11.0 |
| Type: | New Feature | Priority: | Unknown |
| Reporter: | Robert Walters | Assignee: | Ross Lawley |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Quarter: | FY24Q2 | ||||||||||||
| Case: | (copied to CRM) | ||||||||||||
| Documentation Changes: | Needed | ||||||||||||
| Description |
|
Request from the community
we like to persist has a String-Key and a JSON payload. The id for the MongoDB is part of the JSON payload. when we receive a tombstone event, we’d like to delete all records that have the key of the topic in a certain field. Currently this is not possible due to -
PR=https://github.com/mongodb/mongo-kafka/pull/108/files
|
| Comments |
| Comment by Githook User [ 01/May/23 ] |
|
Author: {'name': 'Arne Klein', 'email': 'ArneKlein@users.noreply.github.com', 'username': 'ArneKlein'}Message: Support setting a custom deletewritemode.strategy (#108)
|
| Comment by Ross Lawley [ 14/Sep/22 ] |
|
Moved back to `Needs triage` as it will take approx half a day to action the requested changes in the PR. Mainly adding tests for regression testing. |
| Comment by Ross Lawley [ 14/Sep/22 ] |
|
PR looks good - no tests would require adding. Variable name might be changed to be more readable. |