[
https://issues.apache.org/jira/browse/FLINK-37950?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ferenc Csaky closed FLINK-37950.
--------------------------------
Fix Version/s: mongodb-2.1.0
Resolution: Fixed
[{{e0050b4}}|https://github.com/apache/flink-connector-mongodb/commit/e0050b4a0f9bc6b079a0cbe891339b9e9f612b21]
on main
> MongoDB connector should support ordered option
> -----------------------------------------------
>
> Key: FLINK-37950
> URL: https://issues.apache.org/jira/browse/FLINK-37950
> Project: Flink
> Issue Type: Improvement
> Components: Connectors / MongoDB
> Affects Versions: 1.20.1
> Reporter: Jacob Jona Fahlenkamp
> Assignee: Rahul Teke
> Priority: Major
> Labels: pull-request-available
> Fix For: mongodb-2.1.0
>
>
> The MongoDB connector is slower than expected. When using MongoDB API
> directly, we typically use the ordered(false) option to improve bulk write
> performance:
> [https://www.mongodb.com/docs/drivers/java/sync/current/crud/bulk/#unordered-execution]
> The mongodb connector currently doesn't expose this option. It calls
> bulkWrite without specifying BulkWriteOptions - hence using default options -
> here:
> [https://github.com/apache/flink-connector-mongodb/blob/main/flink-connector-mongodb/src/main/java/org/apache/flink/connector/mongodb/sink/writer/MongoWriter.java#L216]
> The default setting is ordered(true), where mongodb is forced to perform the
> bulk operations in sequence.
> It would be great if there was a connector option to set this mongodb option.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
