You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 19, 2024. It is now read-only.
The same is happening when i do a FULL_IMPORT followed by a LOG_BASED import, despite the following message : time=2022-10-19 14:16:31 name=tap_mongodb level=INFO message=Replication method changed from FULL_TABLE to LOG_BASED, will re-replicate entire collection company-company
I'm pretty much stuck at this point and out of ideas. Would appreciate any help/suggestions, thank you !
The text was updated successfully, but these errors were encountered:
je-kr
changed the title
LOG_BASED import no documents when previous state is empty
LOG_BASED import : no documents imported when previous state is empty
Oct 19, 2022
No - you can setup LOG_BASED replication against MongoDB and the tap will pull data from the oplog starting from the point you initiated processing.
The issue is there isn't currently a way to extract data prior to the first execution of LOG_BASED processing, with future executions using LOG_BASED processing.
Hello,
When using the following command :
tap-mongodb --config pipelinewise-tap-mongodb/config.json --catalog pipelinewise-tap-mongodb/catalog.json | target-postgres --config pipelinewise-target-postgres/config.json
I'm getting the following output :
And the following state is generated :
{"bookmarks": {"company-company": {"last_replication_method": "LOG_BASED"}}}
No documents are imported ...
The same is happening when i do a FULL_IMPORT followed by a LOG_BASED import, despite the following message :
time=2022-10-19 14:16:31 name=tap_mongodb level=INFO message=Replication method changed from FULL_TABLE to LOG_BASED, will re-replicate entire collection company-company
I'm pretty much stuck at this point and out of ideas. Would appreciate any help/suggestions, thank you !
The text was updated successfully, but these errors were encountered: