[IGNITE-12424] Fix default query timeout behavior for thin JDBC

• Type: Bug
• Status: Resolved
• Priority: Blocker
• Resolution: Fixed
• Fix Version/s: 2.8
• Component/s: sql
• Ignite Flags: Docs Required, Release Notes Required
• Assignee: Ivan Pavlukhin
• Reporter: Ivan Pavlukhin
• Created: 09/Dec/19 08:33
• Updated: 17/Dec/19 12:29
• Resolved: 17/Dec/19 08:26

Description

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.

Issue Links

• is caused by: IGNITE-7285 Add default query timeout
• links to: GitHub Pull Request #7122
• links to: GitHub Pull Request #7122