You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Martijn Visser (Jira)" <ji...@apache.org> on 2022/04/10 14:31:00 UTC

[jira] [Commented] (FLINK-27156) [FLIP-171] MongoDB implementation of Async Sink

    [ https://issues.apache.org/jira/browse/FLINK-27156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17520176#comment-17520176 ] 

Martijn Visser commented on FLINK-27156:
----------------------------------------

[~almogtavor] Thanks for opening the ticket. Please be aware that any new connector will have to end up in its own repository and won't be added to Flink's core repo anymore. 

> [FLIP-171] MongoDB implementation of Async Sink
> -----------------------------------------------
>
>                 Key: FLINK-27156
>                 URL: https://issues.apache.org/jira/browse/FLINK-27156
>             Project: Flink
>          Issue Type: New Feature
>            Reporter: Almog Tavor
>            Priority: Major
>
> *User stories:*
> I’d like to use MongoDB as a sink for my data pipeline and I think it'll be appropriate if it would inherit AsyncSinkBase.
> *Scope:*
>  * Implement an asynchronous sink for MongoDb by inheriting the AsyncSinkBase class. The implementation can for now reside in its own module in flink-connectors, or maybe we can open a dedicated repository.
>  * Implement an asynchronous sink writer for MongoDb by extending the AsyncSinkWriter. The implementation must deal with failed requests and retry them. The implementation should batch multiple requests The implemented Sink Writer will be used by the Sink class that will be created as part of this story. I'm currently looking for the right object in the Async MongoDb client that will represent the request.
> h2. References
> More details to be found [https://cwiki.apache.org/confluence/display/FLINK/FLIP-171%3A+Async+Sink]



--
This message was sent by Atlassian Jira
(v8.20.1#820001)