You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@beam.apache.org by "Alex Van Boxel (JIRA)" <ji...@apache.org> on 2018/03/04 17:56: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=16385261#comment-16385261 ] 

Alex Van Boxel commented on BEAM-2639:
--------------------------------------

Is there any movement on this feature. Otherwise I am willing to take this over. As soon as our Mongo cloud provider switches to 3.6 we want to use change-streams.

I have some basic tests working and also have beam mongo IO build as well as the unit tests running.

The only thing I'm a bit worried about is the unit tests, as change streams need a replica-set of mongo's and I think the mongo test framework only supports regular mongo's (I could be wrong though).

> 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: nevi_me
>            Assignee: Jean-Baptiste Onofré
>            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
(v7.6.3#76005)