[
https://issues.apache.org/jira/browse/IGNITE-2680?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15308416#comment-15308416
]
Alexei Scherbakov commented on IGNITE-2680:
-------------------------------------------
Got it working even on killer query like join producing 100M records.
This is achieved by remotely calling PreparedStatement.cancel if an initator
closes the query.
Planning to implement 3 ways to stop running distributed SQL queries:
1) At any time by calling query.close (working, needs more testing)
2) By settings timeout to SQL query using
void setTimeout(long timeout, TimeUnit timeUnit)
3) Globally using H2 properties
jdbc:h2:~/db/test;query_timeout=10000
BTW, It should work without any code modifications, but I haven't chance to
test it yet.
> 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)
