-
Type:
Improvement
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: Aggregation Framework, Performance
-
None
-
Fully Compatible
-
Query 2018-10-22
-
None
-
None
-
None
-
None
-
None
-
None
-
None
We want to avoid making guarantees to the client about which order the updates/inserts are applied in, and how one error impacts which other updates may succeed. Moving to unordered operations should allow for a performance gain in sharded output collections, since we will be able to send large batches instead of repeatedly having to wait for responses before continuing.