Open maxsumrall opened 1 month ago
Good day, @maxsumrall ! Thank you for reporting the issue!
Do you close client at any case? The error indicates that underlying client was closed.
Would you please try configuring client with
.useNewImplementation(true)
- it will switch client to use new HTTP transport layer that we recently tested and it should not have such issue.
Is the remote server Cloud instance? Is there a proxy between client and the server?
Thanks!
Would you please try configuring client with
.useNewImplementation(true)
- it will switch client to use new HTTP transport layer that we recently tested and it should not have such issue.
Sure, I'll investigate using it. Is there any docs about the new and old implementation is?
N.B. This is marked in the code as:
@deprecated - do not use - it is only for development
Is the remote server Cloud instance? Is there a proxy between client and the server?
Yes using CH cloud.
@maxsumrall Initially we have created new client v2 API and had to use old client for testing and trying out the new API. While that time we have developed a new transport layer what is called a "newImplementation". In the future we will remove usage of an old client to deprecate it.
Describe the bug
It appears that the first queries (SELECTs) to the ClickHouse server fail on the V2 client with an error:
com.clickhouse.client.api.ClientException: Failed to get query response
. Wrapping the request in a retry loop seems to resolve after the first failed attempt.Steps to reproduce
3.
Expected behaviour
Query succeeds.
Code example
See above.
Error log
Configuration
Environment
ClickHouse server