I've set the timeout=30, but it seems got no effect. And in impalad /sessions,  I've found the query session's idle timeout(s) is 1800. In /varz both idle session and query timeout are 30. ... View more

It seems that only db_name is needed according to  https://www.cloudera.com/documentation/enterprise/5-15-x/topics/impala_refresh_functions.html Syntax: REFRESH FUNCTIONS db_name   And in 2.X version of impala the only way is to grant all on server to the role, while in  Impala 3.0 and higher  the minimum level of privileges required by refresh functions is to grant refresh on database to the role. SQL Statement Privileges Scope REFRESH FUNCTIONS REFRESH DATABASE https://impala.apache.org/docs/build/html/topics/impala_grant.html ... View more

UDF considerations: In CDH 5.12 / Impala 2.9 and higher, you can refresh the user-defined functions (UDFs) that Impala recognizes, at the database level, by running the REFRESH FUNCTIONS statement with the database name as an argument. Java-based UDFs can be added to the metastore database through Hive CREATE FUNCTION statements, and made visible to Impala by subsequently running REFRESH FUNCTIONS. For example: CREATE DATABASE shared_udfs; USE shared_udfs; ...use CREATE FUNCTION statements in Hive to create some Java-based UDFs that Impala is not initially aware of... REFRESH FUNCTIONS shared_udfs; SELECT udf_created_by_hive(c1) FROM ... ... View more

The user has already got ALL rights on database where the function is built     Syntax: REFRESH FUNCTIONS db_name ... View more

Yes , we use hue as a query interface very often.  What we are concern about is that if the query running in hue last so long , will it occupy the concurrency we have in impala since we have admision control ? ... View more