[SERVER-80386] Refactor jstests/sharding/updateOne_without_shard_key/explain.js Created: 24/Aug/23  Updated: 27/Oct/23  Resolved: 11/Sep/23

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Major - P3
Reporter: Katie Yang (Inactive) Assignee: [DO NOT USE] Backlog - Sharding NYC
Resolution: Gone away Votes: 0
Labels: sharding-nyc-subteam1
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
is duplicated by SERVER-80385 Refactor jstests/sharding/updateOne_w... Closed
Problem/Incident
Related
is related to SERVER-80388 Re-enable jstests/sharding/updateOne_... Closed
Assigned Teams:
Sharding NYC
Participants:
Linked BF Score: 158

 Description   

Currently, the tests written in this file have very specific assertions for test cases. This means that any changes to plan selection may result in the failure of this test, even if the new plan is valid. 

An example is BF-29709, which was caused by a change in multi-planner tie breaking. When this new heuristic is applied, the plans with CLUSTERED_IXSCAN is chosen over ones with FETCH, which resulted in the test failing, despite both plans being valid.

The refactor should ensure that the test passes for all valid plans, not just one of them. This will ensure changes in plan selection do not result in failure.

Point of contact is alexander.ignatyev@mongodb.com as katie.yang@mongodb.com will be off.


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