[CXX-365] Add MCI configuration to test against non-mmapv1 storage engine Created: 06/Oct/14  Updated: 13/Nov/14  Resolved: 06/Nov/14

Status: Closed
Project: C++ Driver
Component/s: Testing
Affects Version/s: None
Fix Version/s: legacy-1.0.0-rc2

Type: Task Priority: Blocker - P1
Reporter: Andrew Morrow (Inactive) Assignee: Spencer Jackson
Resolution: Done Votes: 0
Labels: legacy-cxx
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by DRIVERS-184 add new storage engines to testing ma... Closed
is depended on by DRIVERS-190 Test against non-mmapv1 storage engine Closed

 Description   

We need to ensure that the driver works against alternative storage engines that may not offer certain implementation specific points of interaction.



 Comments   
Comment by Githook User [ 06/Nov/14 ]

Author:

{u'username': u'spencerjackson', u'name': u'Spencer Jackson', u'email': u'spencer.jackson@mongodb.com'}

Message: CXX-365 Test heap1 storage engine
Branch: legacy
https://github.com/mongodb/mongo-cxx-driver/commit/7eb067d7833e8dde9de63f61d203db6db7b1d309

Comment by Spencer Jackson [ 05/Nov/14 ]

https://github.com/mongodb/mongo-cxx-driver/pull/191

Comment by Tyler Brock [ 03/Nov/14 ]

We should consider doing this by creating new configurations upsteam in the MO project that would contain the various storage engine parameters.

This is where the existing json configurations are (for reference):
https://github.com/mongodb/mongo-orchestration/tree/master/mongo_orchestration/configurations

Create a couple of new server, replica_set and sharded_cluster configs named "heap.json", etc... then plumb it through the testing system.

Generated at Wed Feb 07 21:58:59 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.