[DRIVERS-1853] Clustered Indexes for all Collections Created: 15/Jul/21 Updated: 28/Oct/23 Resolved: 13/Feb/23 |
|
| Status: | Closed |
| Project: | Drivers |
| Component/s: | Collection Management |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Backlog - Core Eng Program Management Team | Assignee: | Abraham Egnor |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | size-small, spec-change | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Driver Changes: | Needed | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Server Compat: | 5.3 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Quarter: | FY23Q2 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Upstream Changes Summary: | We're planning to add new fields to command responses and change output of listIndexes. Scope will have more details. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Downstream Changes Summary: | Drivers will need to:
Update: serverless: forbid was added in this commit |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Driver Compliance: |
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Description |
|
Downstream Change Summary We're planning to add new fields to command responses and change output of listIndexes. Scope will have more details. Description of Linked TicketEpic Summary SummaryWithout clustering, a collection is stored in a B-Tree by a RecordId that is not exposed to end users, and there is a primary key index (<primary key>, <RecordId>). With clustering, a collection is to be stored in a B-Tree by the collection’s primary key, and there is no primary key index. This project is a generalization of clustering for time series (PM-288), and will need to support upgrading existing collections to use clustering. MotivationClustering by primary key is important for fast scale in/out in Serverless. This is largely because split and merge, which will do a physical copy such as file copy, will replace tenant migration/chunk migration, which does a logical copy.
General benefits of clustering include:
One downside is clustering may consume more space if there are local secondary indexes, since the primary key index reduces the number of copies of each primary key value Cast of Characters
DocumentationProduct Description |
| Comments |
| Comment by Githook User [ 16/May/22 ] |
|
Author: {'name': 'Jeff Yemin', 'email': 'jeff.yemin@mongodb.com', 'username': 'jyemin'}Message: Add serverless: forbid for collection management tests (#1216)
|
| Comment by Githook User [ 27/Apr/22 ] |
|
Author: {'name': 'Abraham Egnor', 'email': 'abraham.egnor@mongodb.com', 'username': 'abr-egn'}Message: |
| Comment by PM Bot [ 19/Jan/22 ] |
|
If you are not logged in, you can view the tickets in this epic by following this link. |
| Comment by PM Bot [ 18/Aug/21 ] |
|
Moved to Needs Triage because a linked PM issue (PM-2311)was moved to Ready for Work. |