[SERVER-76400] Tests use a non _id clusterKey to test clusteredIndex properties Created: 21/Apr/23  Updated: 27/Oct/23  Resolved: 28/Jun/23

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

Type: Task Priority: Major - P3
Reporter: Haley Connelly Assignee: Haley Connelly
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-62852 Evaluate support for clustering colle... Backlog
Assigned Teams:
Storage Execution
Sprint: Execution EMEA Team 2023-07-10
Participants:

 Description   

A while back, we implemented support for non _id clusterKeys on non-replicated collections. Since then (to my knowledge), we've decided to only support _id clusterKeys.

There are tests we use to validate clusteredIndex behavior which use a non _id clusterKey on a local database.

All tests that use a non _id clusterKey should be re-evaluated / changed to use _id until we decide to add full support for non _id clustered indexes.



 Comments   
Comment by Haley Connelly [ 28/Jun/23 ]

The test mentioned has since been changed. It doesn't look like there are more tests which target an arbitrary cluster key without also testing the same behavior with an "_id" cluster key. 

It's still somewhat confusing to developers of new tests that arbitrary cluster key fields don't have full support (given we have tests like clustered_coll_mod_arbitrary_key.js, which also has an _id counterpart). Hopefully we can either add full support or remove the misleading tests in SERVER-62852

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