Hello, I will appreciate if someone can shed some light on a frequent behavior with hive. We issue queries to hive using hive-jdbc version 2.3.5, our resources on the cluster are managed by YARN. Sometimes , A query is scheduled, and changes states but the client is not getting the state changes. It can be a query that was killed, finished , or stopped. the client hangs getting the status through thrift and remains unaware.
I will appreciate if there is something that can be done or understood in hive what is happening to the query. Maybe hive loses the client connection or sends the response but it's lost and it does not wait for ack and does not retries. thanks. -- Or Gerson -- The above terms reflect a potential business arrangement, are provided solely as a basis for further discussion, and are not intended to be and do not constitute a legally binding obligation. No legally binding obligations will be created, implied, or inferred until an agreement in final form is executed in writing by all parties involved. This email and any attachments hereto may be confidential or privileged. If you received this communication by mistake, please don't forward it to anyone else, please erase all copies and attachments, and please let me know that it has gone to the wrong person. Thanks.
