-
Type:
Bug
-
Resolution: Won't Do
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Query Execution
-
ALL
-
-
None
-
None
-
None
-
None
-
None
-
None
-
None
This is a scenario where running the same command directly on a replicaset's primary of a sharded cluster behaves differently. In this attached snippet, explain represents the output of explain and res represents the output of the command itself.
{
"host": "localhost:20001",
"explain": {
"ok": 0,
"errmsg": "Cannot find index to verify that join fields will be unique",
"code": 51183,
"codeName": "Location51183",
"$clusterTime": {
"clusterTime": Timestamp(1739201529, 56),
"signature":
{"hash": BinData(0, "AAAAAAAAAAAAAAAAAAAAAAAAAAA="), "keyId": NumberLong(0)}
},
"operationTime": Timestamp(1739201529, 51)
},
"res": {
"cursor": {"id": NumberLong(0), "ns": "timeseries_merge.observer_in", "firstBatch": []},
"ok": 1,
"$clusterTime": {
"clusterTime": Timestamp(1739201530, 19),
"signature":
{"hash": BinData(0, "AAAAAAAAAAAAAAAAAAAAAAAAAAA="), "keyId": NumberLong(0)}
},
"operationTime": Timestamp(1739201530, 19)
}
}
Will attach the reproduction scenario below.
- is related to
-
SERVER-18047 Explain on non-existent database should return error
-
- Backlog
-