beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "nevi_me (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (BEAM-2639) Unbounded Source for MongoDB
Date Wed, 29 Nov 2017 17:48:00 GMT

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

nevi_me commented on BEAM-2639:
-------------------------------

Hi JB,

I've started doing some research on how this would work, starting with change streams internals.
I'm collecting my thoughts on paper so far, but I'll move it to a Google doc. I'll address
your questions in this doc.

Thanks

> Unbounded Source for MongoDB
> ----------------------------
>
>                 Key: BEAM-2639
>                 URL: https://issues.apache.org/jira/browse/BEAM-2639
>             Project: Beam
>          Issue Type: Bug
>          Components: sdk-java-extensions
>    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
(v6.4.14#64029)

Mime
View raw message