Loading...

XML

Word

Printable

JSON

Type: New Feature
Resolution: Fixed
Priority: Major - P3
Fix Version/s: 4.9.0
Affects Version/s: None
Component/s: Index Maintenance, Storage
Labels:
None

Backwards Compatibility:
Fully Compatible
Sprint:
Execution Team 2021-02-08, Execution Team 2021-02-22
Linked BF Score:
10
Confidence Status:
None
Work Order:
3

Aha! Reference:
None
Tracking Level:
None
Risk Status:
None
Exec Notes:
None
Goal Name:
None
Goal Link:
None

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

(1 is duplicated by, 1 related to)

Assignee:: Louis Williams
Reporter:: Gregory Wlodarek
Participants:: Githook User, Gregory Wlodarek, Louis Williams
Votes:: 0 Vote for this issue
Watchers:: 3 Start watching this issue

Created:: Jan 22 2021 09:01:43 PM UTC
Updated:: Oct 29 2023 09:58:30 PM UTC
Resolved:: Feb 18 2021 09:31:02 PM UTC
Confidence Status Last Update:: 08/Feb/21 5:04 PM

Details

Description

Attachments

Issue Links

Activity

People

Dates