-
Type:
Improvement
-
Resolution: Done
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: Aggregation Framework, Querying
-
None
-
Fully Compatible
-
v3.4
-
Query 2017-03-27
In order to help users trace output in the logs, the system.profile collection, and db.currentOp() back to their application behavior, we should extend the aggregation command to accept a comment parameter:
db.runCommand({aggregate: "myCollection", pipeline: [{$match: "foo"}], comment: "fooMatch"});
We should require at command parsing time that the comment is a string. Its diagnostic display in the logs/profile/currentOp should be consistent with that for the find command's comment parameter, documented here.
- is related to
-
-
- Closed
-
- related to
-
SERVER-36441 Don't truncate 'comment' command parameter in the slow query logs
-
- Backlog
-