[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:
Documented
Related
related to KAFKA-395 Fix custom Delete write model strateg... Closed
Quarter: FY24Q2
Case:
Documentation Changes: Needed

 Description   

Request from the community

https://www.mongodb.com/community/forums/t/support-for-custom-deletewritemode-strategies-in-kafka-sink/175547

 

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 -

  1. Writing is not possible, since the connector fails on the first tombstone event and stops afterwards
  2. Delete is not possible, since there is no support for substituting the model for the delete case in a fashion similiar to writemodel.strategy

 

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)

KAFKA-320
Branch: master
https://github.com/mongodb/mongo-kafka/commit/382d72958fc083d75f0ca7fb58855cf45e2636fa

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.

Generated at Thu Feb 08 09:06:06 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.