[SERVER-28983] The cluster 'aggregate' command is not registered under Windows --dbg=on --opt=off Created: 26/Apr/17  Updated: 30/Oct/23  Resolved: 27/Apr/17

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: 3.5.6
Fix Version/s: 3.5.7

Type: Bug Priority: Major - P3
Reporter: Kaloian Manassiev Assignee: Kaloian Manassiev
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Sharding 2017-05-08
Participants:

 Description   

Due to the static initializer for 'AggregationRequest::kCommandName' running after that of the 'aggregate' command on mongos, it does not end up getting registered correctly.



 Comments   
Comment by Githook User [ 05/May/17 ]

Author:

{u'username': u'kaloianm', u'name': u'Kaloian Manassiev', u'email': u'kaloian.manassiev@mongodb.com'}

Message: SERVER-28983 Get rid of duplicated code in the aggregation command
Branch: master
https://github.com/mongodb/mongo/commit/fb6cd8b9eca492a38d2a493edc5874734fe4555f

Comment by Githook User [ 27/Apr/17 ]

Author:

{u'username': u'kaloianm', u'name': u'Kaloian Manassiev', u'email': u'kaloian.manassiev@mongodb.com'}

Message: SERVER-28983 Fix undefined behaviour for the 'aggregate' command
Branch: master
https://github.com/mongodb/mongo/commit/eec194e751f6c36e53c241da3a1b42fd4b9b98a1

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