[
https://issues.apache.org/jira/browse/IGNITE-2680?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15341158#comment-15341158
]
Sergi Vladykin commented on IGNITE-2680:
----------------------------------------
1. In GridQueryRequest fieldsCount() still returns 7.
2. Mess with time units: Jdbc requires seconds. Our public API javadoc does not
even mention time units.
3. H2 does not have timeouts per statement, it will be set to the whole
connection and must be reset in the end. So the whole idea of prepStmtReadyClo
looks wrong to me.
I did not look further, lets fix these ones first.
> Terminating running SQL queries
> -------------------------------
>
> Key: IGNITE-2680
> URL: https://issues.apache.org/jira/browse/IGNITE-2680
> Project: Ignite
> Issue Type: Bug
> Affects Versions: 1.5.0.final
> Reporter: Denis Magda
> Assignee: Alexei Scherbakov
> Labels: important
>
> If to start a long running SQL query over a huge cache will millions of
> entries there should be a way terminate it. Even if {{QueryCursor}} is closed
> the query won't be cancelled consuming available resources.
> There should be a way to close a query having using an object that is related
> to it. Seems that ideally we can use {{QueryCursor.close()}} method for that;
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
