You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "Will Morgan (Jira)" <ji...@apache.org> on 2020/01/03 08:17:00 UTC
[jira] [Commented] (BEAM-2639) Unbounded Source for MongoDB
[ https://issues.apache.org/jira/browse/BEAM-2639?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17007294#comment-17007294 ]
Will Morgan commented on BEAM-2639:
-----------------------------------
Hi there, I am keen to assist and provide a use case for testing this as my organisation (and others!) would benefit hugely from streaming directly from Mongo into a quota limited sink like BigQuery.
Has there been any movement on this since 2018?
> Unbounded Source for MongoDB
> ----------------------------
>
> Key: BEAM-2639
> URL: https://issues.apache.org/jira/browse/BEAM-2639
> Project: Beam
> Issue Type: Bug
> Components: io-java-mongodb
> Affects Versions: 2.0.0
> Reporter: Neville Dipale
> Priority: Minor
>
> The current MongoDB source is bounded, which means that we can't build streaming pipelines directly from MongoDB.
> MongoDB publishes changes in each collection through the oplog. Would it be possible to create a connector that reads the oplog to create an unbounded source?
> As an oplog is only available through replication, this creates that dependency. We would need to also consider whether a polling method (using the ObjectId) could be an appropriate fallback.
> Thanks
--
This message was sent by Atlassian Jira
(v8.3.4#803005)