[CXX-2368] Snapshot reads on Secondaries Created: 14/Sep/21  Updated: 28/Oct/23  Resolved: 05/Nov/21

Status: Closed
Project: C++ Driver
Component/s: None
Affects Version/s: None
Fix Version/s: 3.7.0

Type: Improvement Priority: Major - P3
Reporter: Kevin Albertson Assignee: Jesse Williamson (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Epic Link: Snapshot reads on Secondaries

 Description   

Scope



 Comments   
Comment by Githook User [ 05/Nov/21 ]

Author:

{'name': 'Jesse Williamson', 'email': 'jesse.williamson@mongodb.com', 'username': 'chardan'}

Message: CXX-2368 support read concern snapshot (#828)

  • Add snapshot-sessions data.

This commit adds data from CXX-2371, as described here:
https://jira.mongodb.org/browse/CXX-2371

  • Add cmake support for unified session tests.
  • Add slight informational improvements to runner's environment variable
    lookup.
  • remove unnecessary CAPTURE of test file contents
  • fix distinct result
  • pass session argument to count_documents operation
  • pass session argument to runCommand, updateOne, listDatabases, listCollections
  • support listIndexes
  • fix writeConcern parsing
  • use wc majority for inserting initialData
  • apply clang-format
  • Fixup for test; cannot check condition until another bug is patched.
  • Respond to review comments.

Signed-off-by: Jesse Williamson <jesse.williamson@mongodb.com>

Co-authored-by: Kevin Albertson <kevin.albertson@mongodb.com>
Branch: master
https://github.com/mongodb/mongo-cxx-driver/commit/b858c5e18dce80bd9f8919f48b3be6fa3e066332

Comment by Jesse Williamson (Inactive) [ 14/Sep/21 ]

Error checking in the event of both snapshot and causal consistency being set is currently handled in the C library, by mongoc_client_start_session(); this sets up a bson_error_t (via bson_error()) and then (back in the C++ boundary) client_session::impl throws.

It appears that, by design, this is the only way to pass in options, so I believe we already going to implicitly handle an error situation correctly.

Generated at Wed Feb 07 22:05:42 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.