Details
-
Bug
-
Resolution: Unresolved
-
Major - P3
-
None
-
6.0.13
-
None
-
Storage Execution
-
ALL
-
Execution Team 2024-02-19
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 })
|
}
|
Attachments
Issue Links
- related to
-
SERVER-82924 Time-series collections should indicate collection UUID mismatch errors in all cases when they happen.
-
- Open
-