[SERVER-61014] Don't hardcode KeyString version for clustered collections Created: 26/Oct/21  Updated: 27/Feb/23  Resolved: 27/Feb/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: Backlog - Storage Execution Team
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Assigned Teams:
Storage Execution
Sprint: Execution Team 2021-11-29, Execution Team 2022-01-10
Participants:

 Description   

Right now, the generated RecordId uses the default KeyString version

The goal is to remove the hardcoded references to KeyString::Version::kLatestVersion and pip in the version provided upon the clustered collection creation.

It would be nice for validate to also account for the version

 

There is a mapping between the IndexVersion 'v' provided when creating a clusteredIndex and KeyString::Version

IndexVersion :: KeyStringVersion
1 :: 0

2 :: 1



 Comments   
Comment by Connie Chen [ 27/Feb/23 ]

If we ever add a new KeyString version we will revisit all existing uses, so closing as won't do until that happens.

Comment by Louis Williams [ 29/Oct/21 ]

This is mostly a cleanup ticket. We will not support v:1 clustered indexes.

Generated at Thu Feb 08 05:51:19 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.