[SERVER-70789] Rename global indexes related structures and API Created: 24/Oct/22 Updated: 29/Oct/23 Resolved: 05/Mar/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 7.0.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Allison Easton | Assignee: | Marcos José Grillo Ramirez |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | PM-2583-Milestone-3 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Sharding EMEA
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Participants: | |||||||||
| Description |
|
This ticket is to unify naming throughout the sharding global indexes work. It will also change usages of ShardVersion to ChunkVersion where needed. For the global indexes work, we have the following naming scheme as a plan: IndexVersion ==> the timestamp telling when the last modification to global indexes was made CollectionIndexes ==> an object containing both the IndexVersion and the collectionUUID GlobalIndexesInfo ==> a structure holding the CollectionIndexes + the set of indexes for a collection OptionalGlobalIndexesInfo ==> a struct with an optional GlobalIndexesInfo to be stored in the catalog cache _indexCache ==> the portion of the catalog cache relating to global indexes. Additionally after SERVER-71252 there is a way to distinguish between global and non-global indexes in the cache, however, the overall API is globalness agnostic, meaning we could be storing a regular index metadata in the catalog and the API would work the same, so actually we could rename the entire thing to not have the word 'global' in it. |
| Comments |
| Comment by Githook User [ 04/Mar/23 ] |
|
Author: {'name': 'Marcos José Grillo Ramirez', 'email': 'marcos.grillo@mongodb.com', 'username': 'm4nti5'}Message: |