-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
oplogtoredis support #17
Comments
Hi Vlad
We said we are looking into ways to support oplogtoredis - the problem is that it only sends a message of changes to the db (I believe it only provides the doc _id). This meant we have to refetch the doc from Mongo. So as of yet, I don’t see how we can do it without changing oplogtoredis (to transmit the full changes not just the _id)
… On Jul 18, 2021, at 7:29 AM, Vlad Lasky ***@***.***> wrote:
Hi Ramez - another question:
I note this fork of your fork that claims to have implemented a "fix to work with oplogtoredis".
***@***.***
This sounds positive. Do you have any opinions about the modifications in this commit?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
@vlasky |
oplogtoredis support break serious design assumptions. An extra DB query is required to support it. Closing ... |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi Ramez - another question:
I note this fork of your fork that claims to have implemented a "fix to work with oplogtoredis".
https://github.com/crisis24/redis-oplog/commit/fc77c9bf7125d8cc6b11980be643eab7cdd1b836
This sounds positive. Do you have any opinions about the modifications in this commit?
The text was updated successfully, but these errors were encountered: