You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "Jacob Jona Fahlenkamp (Jira)" <ji...@apache.org> on 2024/09/05 11:59:00 UTC

[jira] [Updated] (FLINK-36228) MongoDB sink should be asynchronous

     [ https://issues.apache.org/jira/browse/FLINK-36228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jacob Jona Fahlenkamp updated FLINK-36228:
------------------------------------------
    Description: In our use case, the MongoDB connector is causing a bottle neck, and we see improved performance by implementing a custom mongodb sink. Looking at the code of the flink-connector-mongodb, it appears to me that one issue is that the MongoDB connector is not implemented to be asynchronous.  (was: In our use case, the MongoDB connector is causing a bottle neck, and we see improved performance by implementing our own sink. Looking at the code, it appears to me that one issue is that the mongodb-connector is not implemented to be asynchronous.)

> MongoDB sink should be asynchronous
> -----------------------------------
>
>                 Key: FLINK-36228
>                 URL: https://issues.apache.org/jira/browse/FLINK-36228
>             Project: Flink
>          Issue Type: Improvement
>          Components: Connectors / MongoDB
>    Affects Versions: 1.19.1
>            Reporter: Jacob Jona Fahlenkamp
>            Priority: Major
>
> In our use case, the MongoDB connector is causing a bottle neck, and we see improved performance by implementing a custom mongodb sink. Looking at the code of the flink-connector-mongodb, it appears to me that one issue is that the MongoDB connector is not implemented to be asynchronous.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)