[SERVER-69407] Prevent retryable_writes_nested_shard_key.js from running on storage engines that don't allow document-level locking Created: 02/Sep/22  Updated: 29/Oct/23  Resolved: 06/Sep/22

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 4.2.23, 4.4.17, 6.1.0-rc1

Type: Bug Priority: Major - P3
Reporter: Jennifer Peshansky (Inactive) Assignee: Jennifer Peshansky (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Backwards Compatibility: Fully Compatible
Operating System: ALL
Participants:
Linked BF Score: 59

 Description   

As of SERVER-48312, which landed in v4.7, all storage engines support document-level locking. But on v4.2 and v4.4, this test should be tagged as requires_document_locking to avoid a WriteError.



 Comments   
Comment by Githook User [ 06/Sep/22 ]

Author:

{'name': 'Jennifer Peshansky', 'email': 'jennifer.peshansky@mongodb.com', 'username': 'jenniferpeshansky'}

Message: SERVER-69407 Tag retryable_writes_nested_shard_key.js as requires_document_locking
Branch: v4.2
https://github.com/mongodb/mongo/commit/3bbbb44559e851e2fbc962a644dbf1d53acd1228

Comment by Githook User [ 06/Sep/22 ]

Author:

{'name': 'Jennifer Peshansky', 'email': 'jennifer.peshansky@mongodb.com', 'username': 'jenniferpeshansky'}

Message: SERVER-69407 Tag retryable_writes_nested_shard_key.js as requires_document_locking
Branch: v4.4
https://github.com/mongodb/mongo/commit/39067ac3ef739a47970637e0cbd20250dd0e694d

Generated at Thu Feb 08 06:13:23 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.