[SERVER-40154] change_streams_resume_at_same_clustertime.js should not assume change order Created: 15/Mar/19  Updated: 29/Oct/23  Resolved: 15/Mar/19

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: 4.1.9
Fix Version/s: 4.0.8, 4.1.10

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

Issue Links:
Backports
Depends
Related
is related to SERVER-39900 change_streams_resume_at_same_cluster... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v4.0
Participants:
Linked BF Score: 28

 Description   

As originally written, change_streams_resume_at_same_clustertime.js assumed that an update performed across two shards to a document on each shard would result in changes with the same cluster time. This is not the case and SERVER-39900 adjusted the test to reflect. When making that adjustment we missed removing assertions that the two documents are returned in a specific order.



 Comments   
Comment by Githook User [ 22/Mar/19 ]

Author:

{'name': 'James Wahlin', 'username': 'jameswahlin', 'email': 'james@mongodb.com'}

Message: SERVER-40154 change_streams_resume_at_same_clustertime.js should not assume change order

(cherry picked from commit b6958f06004e45baf0fb4b2593dd6bd2e4765279)
Branch: v4.0
https://github.com/mongodb/mongo/commit/a024594e29523cd3213f6127e120a00c697d0831

Comment by Githook User [ 15/Mar/19 ]

Author:

{'name': 'James Wahlin', 'username': 'jameswahlin', 'email': 'james@mongodb.com'}

Message: SERVER-40154 change_streams_resume_at_same_clustertime.js should not assume change order
Branch: master
https://github.com/mongodb/mongo/commit/b6958f06004e45baf0fb4b2593dd6bd2e4765279

Generated at Thu Feb 08 04:54:10 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.