[
https://issues.apache.org/jira/browse/IGNITE-2674?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15150546#comment-15150546
]
ASF GitHub Bot commented on IGNITE-2674:
----------------------------------------
GitHub user isapego opened a pull request:
https://github.com/apache/ignite/pull/491
IGNITE-2674: Removed cursor removing in OdbcRequestHandler.fetchQuery().
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/isapego/ignite ignite-2674
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/491.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #491
----
----
> ODBC: Cursors should be removed in case of exception only in
> OdbcRequestHandler.executeQuery() method.
> ------------------------------------------------------------------------------------------------------
>
> Key: IGNITE-2674
> URL: https://issues.apache.org/jira/browse/IGNITE-2674
> Project: Ignite
> Issue Type: Sub-task
> Components: odbc
> Affects Versions: 1.5.0.final
> Reporter: Vladimir Ozerov
> Assignee: Igor Sapego
> Fix For: 1.6
>
>
> It is not clear why do we remove query cursor from map in case of exception
> in OdbcRequestHandler.fetchQuery().
> If user has some try-finally construct on the client side and will try to
> close the request after this exception, he will receive another one from
> close() method.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
