The QUERY_TIMEOUT_S also controls the idle query timeout.  The default for that can be set as an impalad startup option (--default_query_options='key,value'), or the value can be set via the SET command, a parameter during session creation, or a default attached to an admission control resource pool.   Note that resources used to execute the query will be reserved until all the query results are fetched (since Impala is a streaming engine, final results are computed "on the fly" while results are fetched), so it's good practice to fetch the results promptly, and set a timeout to help free resources in case results are not fetched. ... View more

I think what you are looking for is this: https://www.simba.com/products/Impala/doc/JDBC_InstallGuide/content/jdbc/options/sockettimeout.htm ... View more

How are you connecting to Impala?  Generally, a connection supports multiple sessions.  A session closing wouldn't imply that the connection would be closed given that the connection can have other sessions.  Session close will free the state associated with that session and close any operations/requests that were made in that session that are still open.  ... View more

Hi,   It is working as expected. Please see the BETWEEN section on: http://www.cloudera.com/content/www/en-us/documentation/enterprise/latest/topics/impala_operators.html   Dan ... View more