ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ignite TC Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-11314) JDBC Thin: add transaction-scoped flag to JdbcHandler's responses.
Date Thu, 11 Apr 2019 13:27:00 GMT

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

Ignite TC Bot commented on IGNITE-11314:
----------------------------------------

{panel:title=--&gt; Run :: All: No blockers found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *--&gt; Run :: All* Results|https://ci.ignite.apache.org/viewLog.html?buildId=3562248&amp;buildTypeId=IgniteTests24Java8_RunAll]

> JDBC Thin: add transaction-scoped flag to JdbcHandler's responses.
> ------------------------------------------------------------------
>
>                 Key: IGNITE-11314
>                 URL: https://issues.apache.org/jira/browse/IGNITE-11314
>             Project: Ignite
>          Issue Type: Task
>          Components: jdbc
>            Reporter: Alexander Lapin
>            Assignee: Alexander Lapin
>            Priority: Major
>              Labels: iep-23
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> Within the context of best effort affinity, and particular, multi-connections, it's necessary
to use "sticky" connections in case of  "next page" requests, transactions, streaming and
copy.
> In order to implement transaction-based-sticky use case we need to know whether we are
in transnational scope or not. So JdbcRequestHandler ought to retrieve query execution plan,
analyse whether transaction exists and propagate corresponding flag to the client.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message