ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aleksey Plekhanov (Jira)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-9410) Add transactions support to thin clients
Date Tue, 03 Sep 2019 12:16:00 GMT

    [ https://issues.apache.org/jira/browse/IGNITE-9410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16921381#comment-16921381

Aleksey Plekhanov commented on IGNITE-9410:

The patch does not change any transaction internals, it just uses transaction almost the same
way as JDBC and ODBC use, (but instead of using transaction per thread approach the new approach
is used with recently implemented suspend/resume mechanism). I'm not sure that review by transactions
expert is needed. [~agoncharuk] WDYT?

> 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

View raw message