[
https://issues.apache.org/jira/browse/IGNITE-12424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16994156#comment-16994156
]
Saikat Maitra commented on IGNITE-12424:
----------------------------------------
[~Pavlukhin]
If we make default query timeout unsupported for thin JDBC client then will
server side configured default query timeout value will still be available for
Ignite servers?
Let's say I started a cluster with server side configured default query timeout
of 10s and then using a JDBC client with 30s client side query timeout then
will my sql query will timeout in 10s or 30s?
IMO, it is still OK to allow query timeout to be different for server and
client for the purpose of few bad client queries with long timeout will still
be protected by default query timeout at server side.
Also, I had another question on SqlFieldsQuery.timeout, Is this also not
available for JDBC client users?
https://github.com/apache/ignite/blob/master/modules/core/src/main/java/org/apache/ignite/cache/query/SqlFieldsQuery.java#L72
> 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)
