About dhecht

dhecht · ‎05-01-2018

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.

dhecht · ‎04-23-2018

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

dhecht · ‎04-20-2018

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.

dhecht · ‎07-07-2017

Impala uses a range get via the S3A connector to download only the column chunks needed.

dhecht · ‎01-14-2016

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

dhecht · ‎01-13-2016

What version of impala are you using? Would you be able to share the impalad.INFO log file when the problem occurs? Regarding question #2: The web UI is the only way to access the query archive from the impalad itself. You can increase the number of queries archived using the --query_log_size, or keep track of all queries by setting the option to -1 (note however, that the archive is kept in memory and so if it's set to -1, the memory usage will continue to grow).

dhecht · ‎08-06-2015

This should not be a problem for Impala because Impala caches metadata and the objects being queried are typically large.

Online	Offline
Last Visited	‎05-02-2018 07:00 PM

Date Registered	‎08-26-2014 01:15 PM
Last Visited	‎05-02-2018 07:00 PM
Total Messages Posted	7
Total Kudos Received	3

Re: Query blah expired due to client inactivity (t...

Re: Expired sessions not closed in Impala

Re: Expired sessions not closed in Impala

Re: Impala query parquet files from S3

Re: impala select with between clause

Re: How to remove query hanging in impala UI?

Re: Partitioned table in s3, best path bucket/path...