You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Aleksey Plekhanov (JIRA)" <ji...@apache.org> on 2019/08/13 07:39:00 UTC
[jira] [Comment Edited] (IGNITE-9410) MVCC: add support to thin
clients
[ https://issues.apache.org/jira/browse/IGNITE-9410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16905889#comment-16905889 ]
Aleksey Plekhanov edited comment on IGNITE-9410 at 8/13/19 7:38 AM:
--------------------------------------------------------------------
The patch is ready, it includes server implementation and java client implementation to support transactions.
[~isapego], there is thin client protocol change in the patch (we discussed it on dev list with you). Could you please review the patch?
was (Author: alex_pl):
The patch is ready.
[~isapego], there is thin client protocol change in the patch (we discussed it on dev list with you). Could you please review the patch?
> 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
> Assignee: Aleksey Plekhanov
> Priority: Major
> Labels: iep-34
> Fix For: 2.8
>
> Time Spent: 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
(v7.6.14#76016)