[SERVER-32567] Replace queryoptimizer3.js with FSM test - MongoDB Jira

XML

Word

Printable

Details

Type: Improvement
Status: Closed
Priority: Major - P3
Resolution: Fixed
Affects Version/s: None
Fix Version/s: 4.2.3, 4.0.14, 4.3.2
Component/s: Querying
Labels:
None

Backwards Compatibility:
Fully Compatible
Backport Requested:

v4.2, v4.0, v3.6
Sprint:
Query 2018-06-18, Query 2018-07-02
Linked BF Score:
45

Description

This test was written a long time ago for ~~SERVER-4400~~. We should consider rewriting it as a C++ unit test or remove it. It does not really work well with the passthrough suites we run these days.

Attachments

Issue Links

is related to

SERVER-4400 attempt to record query plan for a dropped cursor triggers bad file number assertion

Closed

SERVER-31615 Blacklist queryoptimizer3.js from all sharding passthrough suites

Closed

related to

SERVER-43403 Index creation may be allowed to start on a collection in drop-pending state

Closed

SERVER-39224 Explore why queryoptimizer3.js fails using the IndexBuildsCoordinator, then fix it

Closed

SERVER-46872 yield_with_drop.js FSM workload should permit upserts to fail with NoProgressMade

Closed

Activity

People

Assignee:: James Wahlin

Reporter:: Benety Goh

Participants:: Benety Goh, Craig Homa, Githook User, James Wahlin, Kyle Suarez

Votes:: 0 Vote for this issue

Watchers:: 6 Start watching this issue

Dates

Created:: Jan 05 2018 08:34:10 PM UTC

Updated:: Mar 14 2020 02:48:50 AM UTC

Resolved:: Nov 20 2019 08:34:01 PM UTC