[
https://issues.apache.org/jira/browse/IGNITE-11314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16820105#comment-16820105
]
Alexander Lapin commented on IGNITE-11314:
------------------------------------------
[~tledkov-gridgain], could you please take a look?
> 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: 0.5h
> 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)
