You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Vladimir Ozerov (JIRA)" <ji...@apache.org> on 2019/03/11 07:23:00 UTC
[jira] [Updated] (IGNITE-9410) MVCC: add support to thin clients
[ https://issues.apache.org/jira/browse/IGNITE-9410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vladimir Ozerov updated IGNITE-9410:
------------------------------------
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:
# Add API to relevant clients
# Review listener logic - currently we create separate threads. But is it really needed?
## If there is an implicit operation and no ongoing transaction, then operation might be executed right away
## If cache operations are decoupled from threads, then we can resort to reactive approach, when multiple transactions could be executed from the same thread
was:Currently only ODBC and JDBC drivers support transactions. We need to add transactional API to .NET, Java, CPP, NodeJS and Python clients.
> MVCC: add support to thin clients
> ---------------------------------
>
> Key: IGNITE-9410
> URL: https://issues.apache.org/jira/browse/IGNITE-9410
> Project: Ignite
> Issue Type: Task
> Components: mvcc, thin client
> Reporter: Vladimir Ozerov
> Priority: Major
> Fix For: 2.8
>
>
> 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:
> # Add API to relevant clients
> # Review listener logic - currently we create separate threads. But is it really needed?
> ## If there is an implicit operation and no ongoing transaction, then operation might be executed right away
> ## If cache operations are decoupled from threads, then we can resort to reactive approach, when multiple transactions could be executed from the same thread
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)