[1/2] impala git commit: IMPALA-6993: Don't log stack trace in Coordinator::BackendState::Exec()

Repository: impala Updated Branches: refs/heads/master 96c9dac28 -> f976318cc IMPALA-6993: Don't log stack trace in Coordinator::BackendState::Exec() We should use Status::Expected() here, just like it's used above. The stack trace isn't interesting and the error is expected once we get down

[2/2] impala git commit: [DOCS] Fixed a typo in CREATE TABLE syntax

[DOCS] Fixed a typo in CREATE TABLE syntax Change-Id: I968b92dc10d0426fc6295965f909e91b78379522 Reviewed-on: http://gerrit.cloudera.org:8080/10350 Reviewed-by: Alex Rodoni Tested-by: Impala Public Jenkins Project:

[3/5] impala git commit: IMPALA-4850: [DOCS] COMMENT should come after PARTITIONED BY

IMPALA-4850: [DOCS] COMMENT should come after PARTITIONED BY Change-Id: I03fd4a308981955bb52ca79772fe2f7c01b5894f Reviewed-on: http://gerrit.cloudera.org:8080/10316 Reviewed-by: Joe McDonnell Tested-by: Impala Public Jenkins

impala git commit: IMPALA-6908: IsConnResetTException() should include ECONNRESET

Repository: impala Updated Branches: refs/heads/2.x ffac1ab48 -> 33dbdd0bb IMPALA-6908: IsConnResetTException() should include ECONNRESET The utility function IsConnResetTException() attempted to match error strings from RPCs that fail due to the remote end resetting the connection for any

[2/5] impala git commit: [DOCS] Removed the references to YARN as Impala does not support YARN

[DOCS] Removed the references to YARN as Impala does not support YARN Change-Id: Ifcea49b5859a2afbbbe99197e7818c30c7ba6d67 Reviewed-on: http://gerrit.cloudera.org:8080/10346 Reviewed-by: Tim Armstrong Tested-by: Impala Public Jenkins

[1/5] impala git commit: IMPALA-5969: [DOCS] Adds --auth_creds_ok_in_clear to shell options

Repository: impala Updated Branches: refs/heads/master e2e7c103a -> 96c9dac28 IMPALA-5969: [DOCS] Adds --auth_creds_ok_in_clear to shell options This patch adds --auth_creds_ok_in_clear to the impala_shell_options documentation xml Change-Id: I19450ebd839b84a85598d283c04a77662fa5e44e

[4/5] impala git commit: Move admission-controller and catalog metrics into own groups

Move admission-controller and catalog metrics into own groups This makes using these metrics a lot easier since they're not mixed into the big impala-metrics group. Testing: Checked /metrics debug page to see that all metrics were now in a separate section Change-Id:

[3/5] impala git commit: test-with-docker: exit properly on failures

test-with-docker: exit properly on failures If the build was failing, test-with-docker wouldn't recognize it and continue with the script; this fixes that. The bash puzzle I learned here is that bash -c "set -e; function f() { false; echo f; }; if f; then echo x; fi" will print "f" and "x",

[2/5] impala git commit: IMPALA-6946: handle negative counts in RLE decoder

IMPALA-6946: handle negative counts in RLE decoder This improves the handling of out-of-range values to avoid hitting various DCHECKs, including the one in the JIRA. repeat_count_ and literal_count_ are int32_ts. Avoid setting them to a negative value directly or by integer overflow. Switch to

[1/5] impala git commit: IMPALA-6970: race with decreasing scanner reservation

Repository: impala Updated Branches: refs/heads/2.x f55479e07 -> ffac1ab48 IMPALA-6970: race with decreasing scanner reservation The usage pattern of DecreaseReservationTo() in ReturnReservationFromScannerThread() can decrease the reservation by more than 'bytes' if there is a concurrent

[2/2] impala git commit: IMPALA-6948: Delete catalog update topic entries upon catalog restart

IMPALA-6948: Delete catalog update topic entries upon catalog restart This commit fixes an issue where the statestore may end up with stale entries in the catalog update topic that do not correspond to the catalog objects stored in the catalog. This may occur if the catalog server restarts and

[5/5] impala git commit: IMPALA-6948: Delete catalog update topic entries upon catalog restart

IMPALA-6948: Delete catalog update topic entries upon catalog restart This commit fixes an issue where the statestore may end up with stale entries in the catalog update topic that do not correspond to the catalog objects stored in the catalog. This may occur if the catalog server restarts and