-
Type: Bug
-
Resolution: Cannot Reproduce
-
Priority: Major - P3
-
None
-
Affects Version/s: 3.4.7, 3.5.12
-
Component/s: Aggregation Framework, Diagnostics
-
None
-
ALL
Short version: I successfully execute an aggregation framework query, which is logged into system.profile. Copy pasting the pipeline from system.profile back into the mongo shell, and executing against the same mongod instance, fails with various errors. Example error:
assert: command failed: { "ok" : 0, "errmsg" : "$regex has to be a string", "code" : 2, "codeName" : "BadValue" } : aggregate failed _getErrorWithCode@src/mongo/shell/utils.js:25:13 doassert@src/mongo/shell/assert.js:16:14 assert.commandWorked@src/mongo/shell/assert.js:370:5 DBCollection.prototype.aggregate@src/mongo/shell/collection.js:1319:5 @(shell):1:1 2017-08-28T18:13:14.977+0300 E QUERY [thread1] Error: command failed: { "ok" : 0, "errmsg" : "$regex has to be a string", "code" : 2, "codeName" : "BadValue" } : aggregate failed : _getErrorWithCode@src/mongo/shell/utils.js:25:13 doassert@src/mongo/shell/assert.js:16:14 assert.commandWorked@src/mongo/shell/assert.js:370:5 DBCollection.prototype.aggregate@src/mongo/shell/collection.js:1319:5 @(shell):1:1 >
The aggregation pipeline originally comes from the tpch test suite of sqlproxy. I will post a more detailed repro in a dev-only comment.
- is related to
-
SERVER-31098 Wrong ns in system.profile for aggregation query
- Closed