[SERVER-42220] Add a getCheckpointCursor() function to the SortedDataInterface interface and implement it for WiredTiger Created: 12/Jul/19  Updated: 27/Oct/23  Resolved: 31/Jul/19

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

Type: Task Priority: Major - P3
Reporter: Dianna Hohensee (Inactive) Assignee: Backlog - Storage Execution Team
Resolution: Gone away Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by SERVER-42223 Use checkpoint cursors for collection... Closed
Assigned Teams:
Storage Execution
Sprint: Execution Team 2019-08-12
Participants:

 Description   

SortedDataInterface is similar to RecordStore, except SortedDataInterface is the interface through which to access WT tables for our index data and RecordStore is the interface though which to access the WT tables for our collection data. We do not store data in the same format in WT tables for index data as collection data.

We will open a cursor at a WT checkpoint. Read about that here http://source.wiredtiger.com/3.2.0/checkpoint.html.

WT has a WiredTigerCursor class responsible for creating the cursors that indexes use. WiredTigerCursor gets a cursor from the WiredTigerSessionCache. WiredTigerSessionCache is responsible for calling open_cursor against WT. It looks like the validate() function goes through here to here where we use the IndexAccessMethod to instantiate a cursor. WiredTigerCursor appears to open a cursor via one of two WiredTigerSessionCache functions to get cursors.



 Comments   
Comment by Dianna Hohensee (Inactive) [ 26/Jul/19 ]

I expect that to be correct, but have not had a chance to verify it.

Comment by Louis Williams [ 26/Jul/19 ]

dianna.hohensee based on how we're implementing SERVER-42218, I don't think this work is required?

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