[SERVER-80388] Re-enable jstests/sharding/updateOne_without_shard_key/explain.js for internalQueryPlanTieBreakingWithIndexHeuristics Created: 24/Aug/23  Updated: 29/Oct/23  Resolved: 08/Sep/23

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

Type: Task Priority: Major - P3
Reporter: Katie Yang (Inactive) Assignee: Alexander Ignatyev
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-80386 Refactor jstests/sharding/updateOne_w... Closed
Assigned Teams:
Query Optimization
Backwards Compatibility: Fully Compatible
Sprint: QO 2023-09-18
Participants:

 Description   

Currently, this test is skipped when the query knob internalQueryPlanTieBreakingWithIndexHeuristics is on (which is by default), as it fails due to multi-planner tie breaking choosing a plan with CLUSTERED_IXSCAN over FETCH.

Specifically, the following cases fail:

"findAndModify remove with positional projection with sort"
"findAndModify update with positional projection with sort"
"findAndModify update with positional update with sort"

SERVER-80386 will resolve this failure, so one option is to just re-enable this test when it is closed.

Another option is to specifically address the failing cases without refactoring the entire test. Then, the test could also be re-enabled.

The third option is to change multi-planner tie breaking so that the totalDocsExamined heuristic is only applied when plans do not reach EOF in the trial run. This means that this test will no longer be affected and hence can be re-enabled.



 Comments   
Comment by Githook User [ 08/Sep/23 ]

Author:

{'name': 'Alexander Ignatyev', 'email': 'alexander.ignatyev@mongodb.com', 'username': 'aligusnet'}

Message: SERVER-80388 Enable amd make more robust updateOne_without_shard_key/explain.js
Branch: master
https://github.com/mongodb/mongo/commit/7ce770c86289894934666058c83342baa0cad2da

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