-
Type: Task
-
Resolution: Done
-
Priority: Major - P3
-
None
-
Component/s: None
-
None
The intent of this ticket is to find any driver or test problems related to alternative storage engines. Python, Ruby, and Perl all had to rework tests that assumed things about the underlying storage engine that no longer apply with heap1, wired tiger, etc. This should also uncover any places in the driver that access system collections directly instead of through commands. Start the server with "--storageEngine <storage engine name>". The heap1 storage engine is available for testing now.
- depends on
-
CXX-365 Add MCI configuration to test against non-mmapv1 storage engine
- Closed
-
CDRIVER-448 Test against non-mmapv1 storage engine
- Closed
-
CSHARP-1089 Test against non-mmapv1 storage engine
- Closed
-
RUBY-833 Test against wiredTiger storage engine
- Closed
-
PYTHON-781 Run tests against the inMemoryExperiment and wiredtiger storage engines
- Closed
- related to
-
SERVER-15654 Can not initiate a replicaset with newly started mongodb with heap1 storage engine because it already contains data
- Closed
-
SERVER-15942 Replset write-command API test failures for non-mmap engines
- Closed
-
DRIVERS-184 add new storage engines to testing matrix
- Closed