[
https://issues.apache.org/jira/browse/FLINK-27156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17527940#comment-17527940
]
Martijn Visser commented on FLINK-27156:
----------------------------------------
[~almogtavor] We're currently wrapping up moving out our first connector (see
https://github.com/apache/flink-connector-elasticsearch) and now have a better
idea of how a template of an external connector repository would need to look
like.
For a MongoDB connector, I can send out an email to the Dev mailing list and
ask a PMC member to create the repo. This would also include a call for
maintainers, as I think it would be better to have multiple maintainers for
such a connector. What do you think?
> [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
> Components: Connectors / Common
> 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.7#820007)
