[SERVER-33518] aggregate, distinct, filemd5, and geoNear should check out the session Created: 27/Feb/18  Updated: 29/Oct/23  Resolved: 27/Feb/18

Status: Closed
Project: Core Server
Component/s: Storage
Affects Version/s: None
Fix Version/s: 3.7.3

Type: Bug Priority: Major - P3
Reporter: Tess Avitabile (Inactive) Assignee: Tess Avitabile (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Storage NYC 2018-03-12
Participants:
Linked BF Score: 0

 Description   

The distinct and geoNear commands must check out the session because they can contain $where clauses, which require running a find in DBDirectClient to parse, and find checks out the session. The aggregate command must check out the session because it can run geoNear in DBDirectClient. All other commands that allow $where check out the session.

The filemd5 command must check out the session because it can run a find in DBDirectClient.



 Comments   
Comment by Githook User [ 27/Feb/18 ]

Author:

{'email': 'tess.avitabile@mongodb.com', 'name': 'Tess Avitabile', 'username': 'tessavitabile'}

Message: SERVER-33518 aggregate, distinct, filemd5, and geoNear should check out the session
Branch: master
https://github.com/mongodb/mongo/commit/9be3128cbba97456dd70647174a011c0a85ed88b

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