[
https://issues.apache.org/jira/browse/IGNITE-9410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16905887#comment-16905887
]
Ignite TC Bot commented on IGNITE-9410:
---------------------------------------
{panel:title=Branch: [pull/6734/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *--> Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=4491910&buildTypeId=IgniteTests24Java8_RunAll]
> 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)
