[IGNITE-7764] MVCC TX: make cache basic operations support Mvcc tx mode.

• Type: New Feature
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.7
• Component/s: mvcc, sql
• Assignee: Andrey Mashenkov
• Reporter: Roman Kondakov
• Created: 20/Feb/18 11:07
• Updated: 28/Sep/18 13:01
• Resolved: 28/Sep/18 12:58

Description

We need to implement an MVCC-compatible locking protocol for Key-Value API. At the moment during transactions with KV operations if entry we are going to change is unlocked we do not check if it has been changed by the previous transaction. See IGNITE-6935.

 

Lets make get/getAll, put/PutAll/getAndPut, remove/removeAll/getAndRemove operations consistent with SQL queries in MVCC mode at first
as it blocks many other tickets. Other operations can be implemented within separate tickets in parallel once this ticket will be resolved.

Issue Links

• blocks: IGNITE-9224 MVCC SQL: Cache metrics
• blocks: IGNITE-5935 MVCC TX: Tx recovery protocol
• blocks: IGNITE-9321 MVCC: support cache events
• blocks: IGNITE-9540 MVCC TX: make cache invoke\invokeAll operations support Mvcc tx mode.
• blocks: IGNITE-9451 Consistent Cache.size for cache API methods over MVCC tables
• causes: IGNITE-9722 MVCC: Test CacheMvccTransactionTest.testMvccCoordinatorChangeSimple fails.
• causes: IGNITE-9663 MVCC: Data node failure can cause TX hanging.
• is duplicated by: IGNITE-9464 MVCC TX: make cache basic operations support Mvcc tx mode.
• is related to: IGNITE-6935 SQL TX: Locking protocol for simple queries
• links to: GitHub Pull Request #4725
• links to: TC run results