-
Type: Improvement
-
Resolution: Unresolved
-
Priority: Unknown
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
Bulk operations can be run "unordered" which may result in parallel op execution (doc link).
mongo.SessionContext is not safe for use in concurrent code, however (doc link).
To me, it's unclear if this means I may not perform unordered bulk writes within transactions or not ([community question link](https://www.mongodb.com/community/forums/t/sessioncontext-is-not-safe-for-use-in-goroutines-does-this-preclude-unordered-bulk-writes/248644)). I suppose it may be the case that only user-authored parallelism is unsafe, while driver-managed parallelism is handled gracefully?
- related to
-
GODRIVER-716 SessionContext not being goroutine safe is awkward
- Closed