[IGNITE-9410] Add transactions support to thin clients

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.8
• Component/s: mvcc, thin client
• Labels: iep-34 important
• Ignite Flags: Docs Required, Release Notes Required
• Assignee: Aleksey Plekhanov
• Reporter: Vladimir Ozerov
• Created: 29/Aug/18 10:33
• Updated: 28/Jul/20 13:52
• Resolved: 23/Sep/19 07:58

Description

Currently only ODBC and JDBC drivers support transactions and in not very efficient way. We need to add transactional API to .NET, Java, CPP, NodeJS and Python clients.

Key pieces:

1. Add API to relevant clients
2. Review listener logic - currently we create separate threads. But is it really needed?
   1. If there is an implicit operation and no ongoing transaction, then operation might be executed right away
   2. If cache operations are decoupled from threads, then we can resort to reactive approach, when multiple transactions could be executed from the same thread

Issue Links

• is duplicated by: IGNITE-9484 MVCC TX: Handling transactions from multiple threads in jdbc requests handler.
• is related to: IGNITE-11515 MVCC: Make sure that multiple cursors are handled properly for JDBC/ODBC
• is related to: IGNITE-7369 .NET: Thin client: Transactions
• is related to: IGNITE-13308 C++: Thin client transactions
• relates to: IGNITE-5714 Implementation of suspend/resume for pessimistic transactions
• relates to: IGNITE-11514 MVCC: Client listener: do not delegate implicit operation execution to separate thread for JDBC/ODBC
• links to: GitHub Pull Request #6734
• links to: IEP-34