[SERVER-85496] createIndexes ignores collectionUUID for time-series Created: 19/Jan/24  Updated: 30/Jan/24

Status: Open
Project: Core Server
Component/s: None
Affects Version/s: 6.0.13
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Felipe Gasper Assignee: Haley Connelly
Resolution: Unresolved Votes: 0
Labels: time-series
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Problem/Incident
Related
related to SERVER-82924 Time-series collections should indica... Open
Assigned Teams:
Storage Execution
Operating System: ALL
Sprint: Execution Team 2024-02-19
Participants:

 Description   

The `createIndexes` below should fail because the collectionUUID is nonsensical for a time-series collection.

Seen on 6.0.13; I suspect this happens on later versions, too.

> db.createCollection("weather", {timeseries:{timeField:"mytime"}})
{ ok: 1 }
 
> db.runCommand({createIndexes:"weather", collectionUUID: new UUID("f7a43d7b-22d2-4b9c-b1b3-806924034948"), indexes:[{name:"_fg_", key:{mytime:1}}]})
{
  numIndexesBefore: 0,
  numIndexesAfter: 1,
  createdCollectionAutomatically: false,
  commitQuorum: 'votingMembers',
  ok: 1,
  '$clusterTime': {
    clusterTime: Timestamp({ t: 1705695348, i: 1 }),
    signature: {
      hash: Binary(Buffer.from("0000000000000000000000000000000000000000", "hex"), 0),
      keyId: Long("0")
    }
  },
  operationTime: Timestamp({ t: 1705695348, i: 1 })
}


Generated at Thu Feb 08 06:57:53 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.