[SERVER-47516] mode_replace_fail.js should not assume ordering of writes from $merge Created: 13/Apr/20  Updated: 29/Oct/23  Resolved: 01/May/20

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: 4.5.1, 4.4.0-rc1
Fix Version/s: 4.4.0-rc4, 4.7.0

Type: Bug Priority: Major - P3
Reporter: James Wahlin Assignee: Mihai Andrei
Resolution: Fixed Votes: 0
Labels: qexec-team
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
Related
is related to SERVER-46991 Create aggregation secondary reads pa... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v4.4
Sprint: Query 2020-04-20, Query 2020-05-04, Query 2020-05-18
Participants:
Linked BF Score: 19

 Description   

Assertions in this test which assume some ordering of writes from $merge should be relaxed.



 Comments   
Comment by Githook User [ 04/May/20 ]

Author:

{'name': 'Mihai Andrei', 'email': 'mihai.andrei@10gen.com', 'username': 'mtandrei'}

Message: SERVER-47516 mode_replace_fail.js should not assume ordering of writes from $merge

(cherry picked from commit 6f5a00fe5096ceb7d0c2f2e9c0fd19d747c6740d)
Branch: v4.4
https://github.com/mongodb/mongo/commit/e221f26742d91ff1b200e1d068714ae804bd0e28

Comment by Githook User [ 01/May/20 ]

Author:

{'name': 'Mihai Andrei', 'email': 'mihai.andrei@10gen.com', 'username': 'mtandrei'}

Message: SERVER-47516 mode_replace_fail.js should not assume ordering of writes from $merge
Branch: master
https://github.com/mongodb/mongo/commit/6f5a00fe5096ceb7d0c2f2e9c0fd19d747c6740d

Generated at Thu Feb 08 05:14:24 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.