-
Type: New Feature
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Index Maintenance, Storage
-
None
-
Fully Compatible
-
Execution Team 2021-02-08, Execution Team 2021-02-22
-
10
Index tables have an index key -> RecordId (int64_t) layout today. They will need to support the index key -> RecordId (ObjectId) layout so that time-series collections can create secondary indexes.
Determine the type via the durable catalog metadata.
- depends on
-
SERVER-53984 Add metadata for clustered indexes into the durable catalog
- Closed
-
SERVER-53986 Use ObjectId's as table keys for time-series collections
- Closed
-
SERVER-53989 The RecordStore needs to determine its RecordId type via the durable catalog metadata
- Closed
- is depended on by
-
SERVER-54012 Test exportCollection and importCollection for clustered indexes
- Closed
-
SERVER-54013 Verify that an _id index cannot be created when using clustered indexes
- Closed
- is duplicated by
-
SERVER-54247 Investigate renaming RecordStore::isClustered()
- Closed
- related to
-
SERVER-54627 re-enable timeseries_expire.js
- Closed