[SERVER-58949] Support RecordId strings larger than 14 bytes Created: 29/Jul/21  Updated: 29/Oct/23  Resolved: 08/Sep/21

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

Type: Task Priority: Major - P3
Reporter: Louis Williams Assignee: Louis Williams
Resolution: Fixed Votes: 0
Labels: PM-2311-M1
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by SERVER-58436 Implement spilling HashAgg Closed
is depended on by SERVER-59199 Support KeyStrings with RecordId stri... Closed
Problem/Incident
Backwards Compatibility: Fully Compatible
Sprint: Execution Team 2021-08-23, Execution Team 2021-09-06, Execution Team 2021-09-20
Participants:
Linked BF Score: 100

 Description   

Allow RecordId to hold binary strings larger than 14 bytes. This allows RecordStores to be clustered by arbitrarily large keys.

Keep the existing kSmallStr format to optimize storage for small strings. Introduce a new format for larger strings. Consider using a reference-counted buffer that allows RecordId to be cheaply passed around by value.



 Comments   
Comment by Vivian Ge (Inactive) [ 06/Oct/21 ]

Updating the fixversion since branching activities occurred yesterday. This ticket will be in rc0 when it’s been triggered. For more active release information, please keep an eye on #server-release. Thank you!

Comment by Githook User [ 09/Sep/21 ]

Author:

{'name': 'Louis Williams', 'email': 'louis.williams@mongodb.com', 'username': 'louiswilliams'}

Message: SERVER-58949 Don't run clustered_index_types.js on EFT
Branch: master
https://github.com/mongodb/mongo/commit/b59d64efb9d5dff77fc7d01908634331fc8da87d

Comment by Githook User [ 08/Sep/21 ]

Author:

{'name': 'Louis Williams', 'email': 'louis.williams@mongodb.com', 'username': 'louiswilliams'}

Message: SERVER-58949 RecordId supports long strings
Branch: master
https://github.com/mongodb/mongo/commit/2481934027b43267b3bcb521ae029705cb290fdd

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