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
@roman-right we can probably check if client.is_mongos is True here, then run it in session. Otherwise, we can just pass the session as None and make it Optional here
Hi! Hm, this makes sense. The problem is using migrations without transactions is a bit risky as it will not roll back correctly. I probably can add something like --dev flag for the client to run it without transactions if it can not run them
Describe the bug

After upgrading to 1.19.1, we are having issues with running migration locally (on a single instance MongoDB, running on docker).
To Reproduce
Expected behavior
When running locally or without a replica set, this should't run transactions and run into this error.
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: