[KAFKA-394] Delete.on.null.values has no effect Created: 03/Jan/24 Updated: 04/Jan/24 Resolved: 04/Jan/24 |
|
| Status: | Closed |
| Project: | Kafka Connector |
| Component/s: | None |
| Affects Version/s: | 1.11.1 |
| Fix Version/s: | None |
| Type: | Question | Priority: | Unknown |
| Reporter: | Fabian Bell | Assignee: | Ross Lawley |
| Resolution: | Works as Designed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Description |
|
Tombstone messages do not trigger a deletion even if `delete.on.null.values` is set to true. Configuration:
How to reproduce:
Expected behaviour: After ** step 2 we would expect that we do not find any entry with {"_id": "test", ...} in MongoDB. |
| Comments |
| Comment by Ross Lawley [ 04/Jan/24 ] | |||||
|
Excellent, glad its working for you now. Ross | |||||
| Comment by Fabian Bell [ 03/Jan/24 ] | |||||
|
Hi ross@mongodb.com, thank you for the quick response. You are right, the connector receives:
I resolved this issue by adding:
| |||||
| Comment by Ross Lawley [ 03/Jan/24 ] | |||||
|
Are the SMTs are changing the value and making it not null? Specifically:
The connector only gets the record after the SMTs have been applied, so this could make it appear that sink record is not null when it originally was. Ross | |||||
| Comment by PM Bot [ 03/Jan/24 ] | |||||
|
Hi fabianx.bell@gmail.com, thank you for reporting this issue! The team will look into it and get back to you soon. |