-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: Index Maintenance
-
None
-
Fully Compatible
-
ALL
-
v4.0, v3.6
-
Storage NYC 2018-09-24
-
None
-
None
-
None
-
None
-
None
-
None
-
None
applyOps should work with a createIndexes command without a UUID. It currently fails:
> db.adminCommand({applyOps: [{op:"c", ns: "test.$cmd", o: {createIndexes: "test", key: {a:1}, name: "a_1"}}]})
{
"applied" : 1,
"code" : 207,
"codeName" : "InvalidUUID",
"errmsg" : "uuid must be a 16-byte binary field with UUID (4) subtype",
"results" : [
false
],
"ok" : 0,
"operationTime" : Timestamp(1535666215, 1),
"$clusterTime" : ...
}
- is related to
-
TOOLS-2308 MongoDB 4.2 removes applyops handling for system.indexes
-
- Closed
-
-
SERVER-27992 replicate collection UUIDs
-
- Closed
-
- related to
-
SERVER-82349 Mongo 7 crashes on applyOps index delete/drops without a collection UUID
-
- Closed
-
-
SERVER-36015 Remove references to system.namespaces and system.indexes
-
- Closed
-