[SERVER-64824] Clean up Clustered Index Logic Created: 23/Mar/22  Updated: 06/Dec/22  Resolved: 27/Jun/22

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

Type: Improvement Priority: Major - P3
Reporter: Matt Kneiser Assignee: Backlog - Storage Execution Team
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to SERVER-64796 Clustered Index Bug Closed
Assigned Teams:
Storage Execution
Participants:

 Comments   
Comment by Haley Connelly [ 27/Jun/22 ]

The ticket was filed after revisiting the isSpecOKClusteredIndexCheck function.

After changing the scope of what we wanted in the original unique clustered collections project several times, we suspect this method could be simplified in its logic.

It all stemmed from investigating SERVER-64796

Comment by Haley Connelly [ 27/Jun/22 ]

This was a general goal - apologies for letting it slip by. I believe this ticket can be closed for now — as the compound clustered collections project will be changing the code surrounding clustered indexes

Comment by Louis Williams [ 27/Jun/22 ]

matt.kneiser@mongodb.com/haley.connelly@mongodb.com Is there a concrete goal that we can add to the description? Or can we close this ticket?

Comment by Louis Williams [ 19/Apr/22 ]

haley.connelly@mongodb.com, please add a description to this ticket

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