Enable MongoDB sink with unique fields in MongoDB Sharded cluster #135
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Updates:
isUseFilterInValueDoc
) in theMongoDbUpdate
to enable using thefilter
field provided by Debezium.MongoDbUniqueFieldHandler
) to provide default operations with theisUseFilterInValueDoc
enabled.MongoDbHandler
andChangeStreamHandler
to adjust default operations with theisUseFilterInValueDoc
disabled.Problem Statements
Our use case is to migrate data to a new MongoDB Sharded cluster. Our approach is to use CDC (Debezium). When replicating data to the new cluster, we got an error regarding the shard key with the following details.
The current situation is that we have unique fields enabled for some collections in our Sharded cluster. We also use the same unique fields in our new Sharded cluster. The error happened because the MongoDB Sink connector doesn't provide the unique fields information when upserting data.
Solution
As you may know, Debezium provides a
filter
field in its payload, as shown below.Thus, we want to use the
filter
information as a filter when upserting data to solve our problem.