-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Make ChangeStreamOptionsBuilder support startAtOperationTime [DATAMONGO-2607] #3460
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
Comments
Anything I can do to help? |
@johanhaleby If you have some time, a PR would be welcome :) |
@christophstrobl can I make a PR for it? Asking because nothing happened to it from Feb 2021 |
@tudormarc a PR would be welcome :) |
@christophstrobl PR submitted :) |
After having a look, we already support setting |
Johan Haleby opened DATAMONGO-2607 and commented
Newer versions of the MongoDB java driver (and server) supports "startAtOperationTime" for change streams (https://docs.mongodb.com/manual/changeStreams/) to be able to resume a change stream even after an "invalidate" event. But the ChangeStreamOptionsBuilder currently only allows specifying "resumeAt" and not "startAtOperationTime" which prohibits this use case. In the application I'm developing this is really important but I cannot find a workaround when using Spring Data MongoDB.
It would be great if this could be supported by Spring Data MongoDB as well
Affects: 3.1 M1 (2020.0.0), 3.0.2 (Neumann SR2)
Reference URL: https://stackoverflow.com/questions/55184492/difference-between-resumeafter-and-startatoperationtime-in-mongodb-change-stream
The text was updated successfully, but these errors were encountered: