Details
-
Type:
Improvement
-
Status: Closed
-
Priority:
Major - P3
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: 3.5.5
-
Component/s: Aggregation Framework, Querying
-
Labels:None
-
Backwards Compatibility:Fully Compatible
-
Backport Requested:v3.4
-
Sprint:Query 2017-03-27
Description
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.
Attachments
Issue Links
- is documented by
-
DOCS-10020 Docs for SERVER-28128: Add support for a "comment" parameter to the aggregate command
-
- Closed
-
- is related to
-
-
- Closed
-
- related to
-
SERVER-36441 Don't truncate 'comment' command parameter in the slow query logs
-
- Open
-