Member since
09-20-2024
3
Posts
3
Kudos Received
0
Solutions
11-19-2024
05:39 AM
@michalwojtowicz Mentioned error seem to be complaining about expired session which either gets terminated by client or server. Now, to answer your question driver config has SocketTimeout which controls TCP connection: "The number of seconds that the TCP socket waits for a response from the server before raising an error on the request." and default value of the same is 0(i.e the connection does not time out.) Refer: https://docs.cloudera.com/documentation/other/connectors/impala-jdbc/2-6-34/Cloudera-JDBC-Connector-for-Apache-Impala-Install-Guide.pdf However, could you confirm whether you have loadbalancer in place for impala through which you are connecting using JDBC driver? If yes, consider reviewing LB settings which should have timeout configurations allowing server to close the connection for long running queries, for instance: === timeout connect timeout client timeout server ===
... View more
10-03-2024
11:52 AM
Hello- First of all, make sure you are using the latest Impala JDBC connector. If you do - then try to add 'UseNativeQuery=1' to the JDBC connection string and re-test.
... View more
10-03-2024
11:33 AM
Hello- Make sure first of all you are using the latest Cloudera JDBC.
... View more