[SERVER-33979] Test transaction on inMemory and encrypted storage engines Created: 19/Mar/18  Updated: 29/Oct/23  Resolved: 23/Mar/18

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

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

Backwards Compatibility: Fully Compatible
Sprint: Storage NYC 2018-03-26
Participants:

 Description   

Currently, tests for transactions are mostly marked as WiredTiger only. For example, do_txn_basic.js, multi_statement_transaction_simple.js.

However, it is wrong to specifically skip all storage engines that are
not wiredTiger, as that means that we will not test transactions on inMemory and
encrypted storage engines, even if they do support transactions, or if they
start supporting them in the future. Instead we should have a tag that reflects
whether transactions are supported or not.

This way we only have to adjust a single location if we add/remove support for
transactions for a specific storage engine.



 Comments   
Comment by Ian Whalen (Inactive) [ 23/Mar/18 ]

xiangyu.yao did you get an answer about ESE?

Comment by Githook User [ 23/Mar/18 ]

Author:

{'email': 'xiangyu.yao@mongodb.com', 'name': 'Xiangyu Yao', 'username': 'xy24'}

Message: SERVER-33979 Tag fsm transaction test with uses_transaction
Branch: master
https://github.com/mongodb/mongo/commit/877302630e10739e3e3fa0d9c96f45bc437f3660

Comment by William Schultz (Inactive) [ 21/Mar/18 ]

My changes from SERVER-33815 should now run automatically run transactions tests from jstests/core/txns on inMemory storage engines. Coverage for encrypted storage engines, however, does not exist, since we don't have a dedicated Evergreen variant for running with the encrypted storage engine. If this is a supported environment for transactions that we need coverage for, we should probably consider adding a core_txns_ese suite, analogous to the core_ese suite.

Comment by Spencer Brody (Inactive) [ 20/Mar/18 ]

william.schultz, is this handled now with your changes from SERVER-33815?

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