Hi! @MattWho @ggangadharan do you have any insights here? Thanks! ... View more

@pankajgaikwad As this is an older post, you would have a better chance of receiving a resolution by starting a new thread. This will also be an opportunity to provide details specific to your environment that could aid others in assisting you with a more accurate answer to your question. You can link this thread as a reference in your new post. Thanks. ... View more

Hi Ryan, thank you for your quick reply. I'll try the proposed solution, at least because it seems to be the only one to solve the situation. Thanks again ... View more

@cvonschrott Has the reply helped resolve your issue? If so, please mark the appropriate reply as the solution, as it will make it easier for others to find the answer in the future. If you are still experiencing the issue, can you provide the information @ezerihun has requested? Thanks. ... View more

Hi @LucasM , could you describe more of your use case? Your server in GCP have access to Cloudera CML? It's in the same network?   Best Regards ... View more

@weixin   As a test, try using curl and make sure you have a kerberos ticket: curl -u : --negotiate http://YOURHOST:PORT/jmx You may need to open a support case for this. I also highly recommend upgrading to CDP 7.1.9. ... View more

@SAMSAL  Jeez... I should not have prepared that flow at the end of 12 hour work... Of course, it works now, sorry for troubles and thanks for quick support ... View more

Hi, Can you provide sample of this data highlighting what the problem and how do you expect to solve? Also what kind of processor\service are you trying to use to parse this data? ... View more

@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