-
Type: Bug
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: 1.11.1
-
Component/s: Configuration, Sink
-
Not Needed
Hello team,
we are configuring a mongo sink connector using confluent.
My settings were perfect as written in the docs, but only Insert and Update worked, but Delete did not work.
To create the DeleteOneWrite model,
"document.id.strategy" was set to PartialKeyStrategy and allowlist.
Of course "delete.on.null.values" : true ;
"delete.writemodel.strategy" is the default value, DeleteOneDefaultStrategy
But it failed to handle the tombstone event and I found the following bug in MongoSinkTopicConfig:
As mentioned in the docs, with the id strategy to create DeleteOneModel
FullKeyStrategy, PartialKeyStrategy, ProvidedInKeyStrategy
You must create a DeleteOneDefaultStrategy object in one of three ways, but
We discovered something impossible during the current validation process.
Below is the code.
1. DELETE_WRITEMODEL_STRATEGY_CONFIG must be empty to create with 3 id strategies
2. Could not input "" because of Validators.matching(FULLY_QUALIFIED_CLASS_NAME)
3. DELETE_WRITEMODEL_STRATEGY_CONFIG cannot be empty because a default value exists.
Thank you.
- is related to
-
KAFKA-320 Support setting a custom delete writemodel strategy
- Closed