-
Type:
Engineering Test
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: None
-
None
-
Query Optimization
-
None
-
3
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Preferably, the correlated fields can be of any type.
I'm including a list of suggested extensions to the cost model script in case the task of correlated fields would be made easier by also adding other extensions https://docs.google.com/document/d/1fRr-Pg8qkVTu9lz_d12pzDOUwqgECJ7no_-ap2SH8a0/edit?tab=t.0#heading=h.kffq8mg6kf20 Among them, I would guess that giving a choice of data dump and extending the capabilities to specify a desired data set is more important. On the other hand, extending the script to produce indexes and histograms is out of scope because that might end up being a function of query generation instead.
- causes
-
SERVER-106804 Update codeowners for QO benchmarks README
-
- In Code Review
-
- depends on
-
SERVER-104202 Explore merging correlated data generation work with existing data generator
-
- In Code Review
-
-
SERVER-104201 Document correlated data generation work
-
- In Progress
-
-
SERVER-104198 Explore correlated data generation with faker/mimesis
-
- Closed
-
-
SERVER-104199 Explore S3 as a storage target for generated workloads
-
- Closed
-
-
SERVER-104200 Explore using mongodump/mongorestore for working with generated datasets
-
- Closed
-