[
https://issues.apache.org/jira/browse/IGNITE-4192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16283683#comment-16283683
]
Alexander Paschenko edited comment on IGNITE-4192 at 12/8/17 2:55 PM:
----------------------------------------------------------------------
[~vozerov]
My questions/clarifications:
5 - this is done already, see usages of {{IgniteH2Indexing#sqlUserTxStart()}}
{quote}
Most probably transaction should be bound to Connection object.
{quote}
This is what effectively happening now - each {{Connection}} has its own
{{JdbcRequestHandler}} on server side which in turn has single threaded worker
within whose scope transactions start and end. After all, it's a thin client,
and there may be no Ignite running at all on the host owning {{Connection}}
object. All in all, a connection may not have more than one transaction started
as long as no single thread can.
was (Author: al.psc):
[~vozerov]
My questions/clarifications:
5 - this is done already, see usages of {{IgniteH2Indexing#sqlUserTxStart()}}
{quote}
Most probably transaction should be bound to Connection object.
{quote}
This is what effectively happening now - each {{Connection}} has its own
{{JdbcRequestHandler}} on server side which in turn has single threaded worker
within whose scope transactions start and end. After all, it's a thin client,
and there may be no Ignite running at all on the host owning {{Connection}}
object.
> SQL TX: JDBC driver support
> ---------------------------
>
> Key: IGNITE-4192
> URL: https://issues.apache.org/jira/browse/IGNITE-4192
> Project: Ignite
> Issue Type: Task
> Components: jdbc
> Reporter: Denis Magda
> Assignee: Alexander Paschenko
> Labels: iep-3, sql
> Fix For: 2.4
>
>
> To support execution of DML and SELECT statements inside of a transaction
> started from JDBC driver side.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
