[SERVER-30318] Sessions shouldn't require using legacy find path Created: 25/Jul/17  Updated: 30/Oct/23  Resolved: 31/Jul/17

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: 3.5.11

Type: Bug Priority: Major - P3
Reporter: Mathias Stearn Assignee: Randolph Tan
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-28509 Make DBClient use commands for all op... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Sharding 2017-07-31, Sharding 2017-08-21
Participants:

 Description   

Sessions currently require forcibly using the OP_QUERY find path internally when fetching data to avoid recursively calling itself in the find command path. For SERVER-28509, I tagging all of the finds that force using OP_QUERY with a comment including this ticket.



 Comments   
Comment by Githook User [ 31/Jul/17 ]

Author:

{'email': 'randolph@10gen.com', 'username': 'renctan', 'name': 'Randolph Tan'}

Message: SERVER-30318 Remove workaround for multiple instances of OperationContextSession per OperationContext
Branch: master
https://github.com/mongodb/mongo/commit/3cecc93793e62bc0451a04553e0ddb0df259fd1d

Comment by Randolph Tan [ 31/Jul/17 ]

cr: https://mongodbcr.appspot.com/145800001/

Comment by Githook User [ 28/Jul/17 ]

Author:

{'email': 'randolph@10gen.com', 'username': 'renctan', 'name': 'Randolph Tan'}

Message: SERVER-30318 Allow multiple instances of OperationContextSession per OperationContext
Branch: master
https://github.com/mongodb/mongo/commit/9abf0ffe9f50d069078b5cb708cc8aaf518f5405

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