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.