[SERVER-37217] Create aggregation fuzzer mode for checking query correctness with allPaths indexes Created: 19/Sep/18  Updated: 27/Oct/23  Resolved: 03/Oct/18

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

Type: Improvement Priority: Major - P3
Reporter: Ian Boros Assignee: Yuta Arai
Resolution: Gone away Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-37432 Re-enable aggregation_wildcard_fuzzer... Closed
Sprint: Query 2018-10-08
Participants:

 Description   

The aggregation fuzzer lets us compare the results of queries between old versions of mongod and new versions to let us find query correctness bugs. Since allPaths indexes are particularly prone to causing correctness bugs, we should extend the agg fuzzer so that it compare query results between a mongod which has an allPaths index and a mongod which doesn't.

This will involve
1) Making some changes to the agg fuzzer repo (may need a TIG ticket)
2) Adding a .yml in buildscripts/resmokeconfig for the new mode



 Comments   
Comment by David Storch [ 03/Oct/18 ]

Changing the resolution to "Gone Away", since the work originally committed under this ticket as been reverted. Remaining work for the aggregation_wildcard_fuzzer task is now tracked by SERVER-37432.

Comment by Githook User [ 02/Oct/18 ]

Author:

{'name': 'Ian Boros', 'email': 'ian.boros@10gen.com'}

Message: Revert "SERVER-37217 Create aggregation fuzzer mode for checking query correctness with allPaths indexes"

This reverts commit 6c5a7bb094cae90823bd05d8d21074cf2ea79990.
Branch: master
https://github.com/mongodb/mongo/commit/23d7c89e501d221a41f350b0b10a52a4f05bb2e2

Comment by Githook User [ 02/Oct/18 ]

Author:

{'name': 'yarai', 'email': 'yuta.arai@10gen.com', 'username': 'yarai'}

Message: SERVER-37217 Create aggregation fuzzer mode for checking query correctness with allPaths indexes
Branch: master
https://github.com/mongodb/mongo/commit/6c5a7bb094cae90823bd05d8d21074cf2ea79990

Comment by David Storch [ 26/Sep/18 ]

Initial guess at what we should do here is to create a new task called aggregation_wildcard_index_fuzzer. Using the same version of the server (master), this would compare the results of running a query against a collection that has several generated non-wildcard index with running against a collection that has only the index {$**: 1}.

yuta.arai@mongodb.com, we should discuss this plan with max.hirschhorn before you get started, in order to make sure he is on board with this proposal. Also, ian.boros can help you get set up with the jstestfuzz code.

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