[SERVER-33716] $comment is internally converted to a string Created: 07/Mar/18  Updated: 06/Dec/22  Resolved: 23/Oct/19

Status: Closed
Project: Core Server
Component/s: Querying
Affects Version/s: 3.4.13
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: David Bartley Assignee: Backlog - Query Team (Inactive)
Resolution: Duplicate Votes: 0
Labels: query-44-grooming, storch
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Duplicate
duplicates SERVER-29794 Adding a comment to all commands Closed
Related
related to SERVER-27438 Legacy query via mongos drops $comment Closed
Assigned Teams:
Query
Operating System: ALL
Backport Requested:
v3.6, v3.4
Participants:

 Description   

Previously, $comment was permitted to be any type. Per SERVER-27438, 3.4 changed that so that $comment is converted to a string internally. This breaks application that were depending on $comment being a document (in our case, we store things like caller information and tracing spans in $comment). We extract this information from the system.profile log and inprog.

Separately, it seems like the comment field in the find and aggregate commands should similarly accept a document.



 Comments   
Comment by Bernard Gorman [ 23/Oct/19 ]

This feature request is fulfilled by SERVER-29794, which allows comments of any type to be attached to any command. Closing as a dupe of that ticket.

Generated at Thu Feb 08 04:34:20 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.