[2/5] impala git commit: IMPALA-6667: [DOCS] max_cached_file_handles is enabled by default

IMPALA-6667: [DOCS] max_cached_file_handles is enabled by default Change-Id: I61b1dc10c61415c673b49d339ba0d27f6a32a51e Reviewed-on: http://gerrit.cloudera.org:8080/9915 Reviewed-by: Alex Behm Tested-by: Impala Public Jenkins Project:

[4/5] impala git commit: IMPALA-6650: Add fine-grained DROP privilege

IMPALA-6650: Add fine-grained DROP privilege Add support for executing DROP statements by granting DROP privilege. These are the new GRANT/REVOKE statements introduced at server, database, and table scopes. GRANT DROP on SERVER svr TO ROLE testrole; GRANT DROP on DATABASE db TO ROLE testrole;

[5/5] impala git commit: IMPALA-6792: Fail status reporting if coordinator refuses connections

IMPALA-6792: Fail status reporting if coordinator refuses connections The ReportExecStatusAux() function is run on a dedicated thread per fragment instance. This thread will run until the fragment instance completes executing. On every attempt to send a report to the coordinator, it will attempt

[1/5] impala git commit: IMPALA-6571: NullPointerException in SHOW CREATE TABLE for HBase tables

Repository: impala Updated Branches: refs/heads/master cf76953cc -> 890bd4c72 IMPALA-6571: NullPointerException in SHOW CREATE TABLE for HBase tables This patch fixes the NullPointerException in SHOW CREATE TABLE for HBase tables. Testing: - Moved the content of back

[4/5] impala git commit: IMPALA-4430: Update build scripts to die hard when IMPALA_HOME has spaces

IMPALA-4430: Update build scripts to die hard when IMPALA_HOME has spaces Change-Id: I08b3d2b3f3e14c568d1672ee86ff2c52e8017b81 Reviewed-on: http://gerrit.cloudera.org:8080/9385 Reviewed-by: Tim Armstrong Tested-by: Impala Public Jenkins Project:

[5/5] impala git commit: IMPALA-6785: reset failed heartbeat count when re-registering

IMPALA-6785: reset failed heartbeat count when re-registering When a subscriber re-registers with the same subscriber ID, we need to reset failure detection info so that we don't erroneously think that the subscriber has failed. The bug is a mix-up between whether the subscriber or registration