[
https://issues.apache.org/jira/browse/FLINK-35616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jiabao Sun resolved FLINK-35616.
--------------------------------
Fix Version/s: mongodb-1.3.0
Resolution: Implemented
mongodb-connector main: a2f1083c2b0020cde626681e4ebcd0bec649547c
> Support upsert into sharded collections for MongoRowDataSerializationSchema
> ---------------------------------------------------------------------------
>
> Key: FLINK-35616
> URL: https://issues.apache.org/jira/browse/FLINK-35616
> Project: Flink
> Issue Type: Improvement
> Components: Connectors / MongoDB
> Affects Versions: mongodb-1.2.0
> Reporter: Jiabao Sun
> Assignee: Jiabao Sun
> Priority: Major
> Labels: pull-request-available
> Fix For: mongodb-1.3.0
>
>
> {panel:}
> For a db.collection.update() operation that includes upsert: true and is on a
> sharded collection, the full sharded key must be included in the filter:
> * For an update operation.
> * For a replace document operation (starting in MongoDB 4.2).
> {panel}
> https://www.mongodb.com/docs/manual/reference/method/db.collection.update/#upsert-on-a-sharded-collection
> We need to allow users to configure the full sharded key field names to
> upsert into the sharded collection.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
