[COMPASS-7579] Investigate changes in SERVER-77112: shardCollection and createIndex create different indexes on time-series buckets collections Created: 16/Jan/24 Updated: 22/Jan/24 |
|
| Status: | Needs Triage |
| Project: | Compass |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Investigation | Priority: | Major - P3 |
| Reporter: | Backlog - Core Eng Program Management Team | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Developer Tools
|
||||||||
| Epic Link: | COMPASS-7048 | ||||||||
| Description |
|
Original Downstream Change Summary
Description of Linked TicketIf you create a sharded time-series collection using the shardCollection command that has a shardKey {timeField: 1} the resulting index in the buckets collection will have the key { control.min.time: 1.0 }. However, calling the createIndex command on a sharded time-series collection with the same key {timeField: 1} results in an index in the buckets collection with the key { control.min.time: 1.0, control.max.time: 1.0 }. These two indexes have the same key for the view backing the buckets collection. We should investigate if these two commands should produce indexes with the same keys for the buckets collection. Here is a file to reproduce this [^SERVER-77112.js] |
| Comments |
| Comment by PM Bot [ 16/Jan/24 ] |
|
Fix Version updated for upstream |