ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alexander Lapin (JIRA)" <j...@apache.org>
Subject [jira] [Created] (IGNITE-11314) JDBC Thin: add transaction-scoped flag to JdbcHandler's responses.
Date Wed, 13 Feb 2019 14:43:00 GMT
Alexander Lapin created IGNITE-11314:
----------------------------------------

             Summary: 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


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