[GODRIVER-684] Refactor parsing of cursor documents Created: 10/Dec/18  Updated: 27/Oct/23  Resolved: 10/May/19

Status: Closed
Project: Go Driver
Component/s: Core API
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Major - P3
Reporter: Divjot Arora (Inactive) Assignee: Unassigned
Resolution: Gone away Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Epic Link: Core API

 Description   

Currently, the raw response from the server, which contains a cursor subdocument, is passed directly to the newCursor function. This means a new function has to be added to create a cursor for legacy servers because the relevant information (cursor ID, first batch, namespace) is returned in the OP_REPLY struct instead of a document.

Refactor cursor creation so the document parsing happens elsewhere and passes relevant information to newCursor.



 Comments   
Comment by Divjot Arora (Inactive) [ 10/May/19 ]

I filed this ticket when doing legacy support in the old driver library because the information needed to create a cursor is returned differently in legacy and non-legacy server versions. For the new core API, the legacy operations all upconvert the necessary OP_REPLY fields into a cursor document, so this ticket is no longer necessary.

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