[jira] [Commented] (IGNITE-12424) Fix default query timeout behavior for thin JDBC

["Ivan Pavlukhin (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/IGNITE-12424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16993361#comment-16993361 ] 

Ivan Pavlukhin commented on IGNITE-12424:
-----------------------------------------

[~samaitra], unfortunately thin JDBC timeout is not passed from client to server. But there can be a workaround, effectively making default query timeout unsupported for thin JDBC. It is very simple, I prepared a draft PR https://github.com/apache/ignite/pull/7122

> Fix default query timeout behavior for thin JDBC
> ------------------------------------------------
>
>                 Key: IGNITE-12424
>                 URL: https://issues.apache.org/jira/browse/IGNITE-12424
>             Project: Ignite
>          Issue Type: Bug
>          Components: sql
>            Reporter: Ivan Pavlukhin
>            Priority: Blocker
>             Fix For: 2.8
>
>
> After IGNITE-7285 there appeared a buggy behavior for thin JDBC driver. 
> Thin JDBC handles explicit query timeout on a client side. Default query timeout is tracked on a server side. As a server is not aware of explicit client timeout it is not possible to override a default timeout with longer explicit timeout (effectively a query will be cancelled after a default timeout expiration).
> The expected behavior is that an explicit query timeout always overrides a default one.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)