[SERVER-28543] Add OperationContext as an argument to Database::getCollection Created: 29/Mar/17  Updated: 06/Dec/17  Resolved: 06/Apr/17

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

Type: Task Priority: Major - P3
Reporter: Maria van Keulen Assignee: Maria van Keulen
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by SERVER-27988 Add name/UUID cache to OperationContext Closed
Backwards Compatibility: Fully Compatible
Sprint: Storage 2017-04-17
Participants:

 Description   

SERVER-27988 requires that the current OperationContext be accessible from Database::getCollection() since the namespace/UUID cache is a decoration of OperationContext.



 Comments   
Comment by Githook User [ 06/Apr/17 ]

Author:

{u'username': u'mvankeulen94', u'name': u'Maria van Keulen', u'email': u'maria@mongodb.com'}

Message: SERVER-28543 Add OperationContext as an argument to getCollection
Branch: master
https://github.com/mongodb/mongo/commit/1cbb67b8acf6c579a8ef99f9b3bf74394bbd11c3

Comment by Maria van Keulen [ 29/Mar/17 ]

Each OperationContext needs its own namespace/UUID cache, so the cache needs to be a decoration of the OperationContext.

Comment by Kaloian Manassiev [ 29/Mar/17 ]

Is it a decoration of the OperationContext or of the ServiceContext? Because if it is a decoration on the latter you could just start storing the ServiceContext as a member on the Database object and avoid having to thread through OperationContext for every single call to getCollection.

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