You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Ivan Pavlukhin (Jira)" <ji...@apache.org> on 2019/09/01 04:03:00 UTC
[jira] [Commented] (IGNITE-9410) Add transactions support to thin
clients
[ https://issues.apache.org/jira/browse/IGNITE-9410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16920274#comment-16920274 ]
Ivan Pavlukhin commented on IGNITE-9410:
----------------------------------------
[~alex_pl], I must say that I did not check the patch thoroughly. But at least I have not noticed any blockers from a bird-eye view.
> Add transactions 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
> Assignee: Aleksey Plekhanov
> Priority: Major
> Labels: iep-34
> Fix For: 2.8
>
> Time Spent: 3h 10m
> Remaining Estimate: 0h
>
> 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
(v8.3.2#803003)