-
Notifications
You must be signed in to change notification settings - Fork 373
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
Support OpLog #76
Comments
Hello! We have been sort of following this project with interest/excitement for a while, and are potentially interested in using FerretDB with a Meteor app to escape a presently extremely old version of MongoDB as a dependency. Do you have any ballpark how far out Meteor compatibility for FerretDB might be in your present plans? |
Hm, in this blog post it says:
So what does this mean? Is oplog supported or not? Because from reading the post I understood that Meteor (and oplog) support is already available. |
Meteor fallbacks to polling when OpLog is not available. It is not suitable for many production deployments, but sometimes it is good enough. In that case, Meteor applications could work with FerretDB, and indeed some of them work. |
I just found out another library in Go similar to FerretDb and with already support for Oplog, it's called lungo. |
I'm not sure how advanced this effort is, but I wanted to cross-post meteor/meteor#12150 (reply in thread) here:
In other words: #175 is enough for Meteor apps, as long as they want to work with |
The first version with OpLog support is out! See https://github.com/FerretDB/FerretDB/releases/tag/v1.18.0 |
We want to support a subset MongoDB's OpLog that is enough for applications and frameworks tailing it, such as Meteor.
It is not a goal (yet) to make it good enough for replication.
See:
We should support the "old" format, with full
$set
for updates, not the new format withdiff
.Tasks
i
/u
/d
documents into OpLog #3556The text was updated successfully, but these errors were encountered: