RFE: option to avoid exception when query timeout is reached
- Dominant language
- Java
- Stars
- 6.1k
- Forks
- 1.5k
- Avg merge
- 2d 55m
- Merged PRs (30d)
- 182
Description
Based on behavior difference between 0.9.0 and latest version.
Query like this
```SELECT DISTINCT account_key FROM point_entry WHERE MAP_VALUE(account_fields_keys, 'type', account_fields_values) = 'manual_billing_uncollected' and created_at >= 1680566400 LIMIT 11 option(timeoutMs=20000)```
in this case the entire query would have taken much longer than the timeout to finish.
On 0.9.0, when timeout reached, it was able to simply return data it gathered so far and respond to client
But on the latest version, it throw TimeoutException on client side, while retrying the query on controller UI, it returns
```
{
"errorCode": 427,
"message": "207 servers [...] not responded"
}
```
request an option to avoid exception when query timeout is reached
Contributor guide
Research direction
Start with the supplied SELECT query and compare timeout behavior between 0.9.0 and the latest version, including the controller UI retry response. Define and validate the requested option so a timeout can return data gathered so far instead of a client TimeoutException; the issue is done when that behavior is reproducibly tested.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- databases, distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100