[2/4] impala git commit: IMPALA-6710: [DOCS] Update the Partition Insert content

2018-04-11 Thread tarmstrong
IMPALA-6710: [DOCS] Update the Partition Insert content Added a section at the end for inserting into partitioned tables. Change-Id: I4ccc8227579dabc321a949da95e8a59158528f20 Reviewed-on: http://gerrit.cloudera.org:8080/9977 Reviewed-by: Thomas Tauber-Marshall Tested-by:

impala git commit: Add --partial_ok to compare_branches.py.

2018-04-11 Thread tarmstrong
Repository: impala Updated Branches: refs/heads/2.x eaab248ee -> 851f622bf Add --partial_ok to compare_branches.py. This change lets compare_branches.py succeed with a partial set of cherry-picks. In our case, we sometimes get baacked up with several commits needing to be cherry-picked. The

[4/4] impala git commit: Add --partial_ok to compare_branches.py.

2018-04-11 Thread tarmstrong
Add --partial_ok to compare_branches.py. This change lets compare_branches.py succeed with a partial set of cherry-picks. In our case, we sometimes get baacked up with several commits needing to be cherry-picked. The first few cherry-pick fine, and there's a problematic commit sometime down the

[3/4] impala git commit: IMPALA-6623: [DOCS] ltrim and rtrim docs updated

2018-04-11 Thread tarmstrong
IMPALA-6623: [DOCS] ltrim and rtrim docs updated Change-Id: If4f7a04e3c64eade7a23cded21de5ff91c9c8c8c Reviewed-on: http://gerrit.cloudera.org:8080/9984 Reviewed-by: Zoram Thanga Reviewed-by: Alex Rodoni Tested-by: Impala Public Jenkins

[1/4] impala git commit: IMPALA-6831: [DOCS] Remove the note about TLS1.2 on RHEL 6 and CentOS 6

2018-04-11 Thread tarmstrong
Repository: impala Updated Branches: refs/heads/master 818cd8fa2 -> 242e822ae IMPALA-6831: [DOCS] Remove the note about TLS1.2 on RHEL 6 and CentOS 6 Change-Id: I710dd809e6a3f8dee89f4ed8997bba0c2aa2c783 Reviewed-on: http://gerrit.cloudera.org:8080/9983 Reviewed-by: Sailesh Mukil

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

2018-04-11 Thread tarmstrong
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

[24/28] impala git commit: Remove Yarn from minicluster by default. (2nd try)

2018-04-11 Thread tarmstrong
Remove Yarn from minicluster by default. (2nd try) Remove Yarn from minicluster by default. Turns out that we start Yarn as part of the minicluster, but we never use it. (HiveServer2 is configured to run MR jobs "locally" in process.) Likely, this Yarn integration is a vestige of Yarn/Llama

[11/28] impala git commit: IMPALA-4168: [DOCS] Adds Oracle-style hint placement for INSERT/UPSERT

2018-04-11 Thread tarmstrong
IMPALA-4168: [DOCS] Adds Oracle-style hint placement for INSERT/UPSERT Change-Id: I43e0a782087c2e67f2e012424fb9261be445efc9 Reviewed-on: http://gerrit.cloudera.org:8080/9030 Reviewed-by: Alex Rodoni Reviewed-by: Kim Jin Chul Reviewed-by: John Russell

[03/28] impala git commit: IMPALA-6719: Reset metadata database name case sensitivity

2018-04-11 Thread tarmstrong
IMPALA-6719: Reset metadata database name case sensitivity Fix issue with database case name case sensitivity in reset metadata statement. Testing: - Created end-to-end reset metadata tests. Change-Id: Id880aa559cec0afe8fbb7d33ccce83f7b5e474cb Reviewed-on: http://gerrit.cloudera.org:8080/9788

[21/28] impala git commit: IMPALA-6070: Expose using Docker to run tests faster.

2018-04-11 Thread tarmstrong
IMPALA-6070: Expose using Docker to run tests faster. Allows running the tests that make up the "core" suite in about 2 hours. By comparison, https://jenkins.impala.io/job/ubuntu-16.04-from-scratch/buildTimeTrend tends to run in about 3.5 hours. This commit: * Adds "echo" statements in a few

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

2018-04-11 Thread tarmstrong
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:

[01/28] impala git commit: IMPALA-6688: [DOCS] compact_catalog_topic setting is enabled by default

2018-04-11 Thread tarmstrong
Repository: impala Updated Branches: refs/heads/2.x 851f622bf -> bbe534298 IMPALA-6688: [DOCS] compact_catalog_topic setting is enabled by default - Marked IMPALA-5500 as fixed in Impala 2.10 in the impala_known_issues. xml - In the same section, removed the mention of default setting being

[17/28] impala git commit: IMPALA-6711: loosen shell test prompt regex

2018-04-11 Thread tarmstrong
IMPALA-6711: loosen shell test prompt regex We have seen this test fail because the fully-qualified domain name differed between the python test process and the impala shell process (see JIRA for details). The exact domain name is irrelevant to the test - we only really care about whether the

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

2018-04-11 Thread tarmstrong
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:

[22/28] impala git commit: IMPALA-6457: [DOCS] DECIMAL support for Kudu tables

2018-04-11 Thread tarmstrong
IMPALA-6457: [DOCS] DECIMAL support for Kudu tables Removed DECIMAL from the unsupported data types for Kudu. Change-Id: I5a2498b4a28c2a53a3fec9b634a770e42dcac499 Reviewed-on: http://gerrit.cloudera.org:8080/9918 Reviewed-by: Grant Henke Reviewed-by: Alex Behm

[12/28] impala git commit: IMPALA-6389: Make '\0' delimited text files work

2018-04-11 Thread tarmstrong
IMPALA-6389: Make '\0' delimited text files work Initially I didn't want to fully implement this, as the metadata for these tables can't even be fully stored in Postgres; however after digging into some older documentation, it appears that the ASCII NUL character actually has been used as a field

[19/28] impala git commit: [DOCS] Removed old files no longer in use

2018-04-11 Thread tarmstrong
[DOCS] Removed old files no longer in use Change-Id: Ia0aaa756bf0fc0092186ebc293543408b403aa5e Reviewed-on: http://gerrit.cloudera.org:8080/9938 Reviewed-by: John Russell Tested-by: Impala Public Jenkins Project:

[28/28] impala git commit: IMPALA-6805: Show current database in Impala shell prompt

2018-04-11 Thread tarmstrong
IMPALA-6805: Show current database in Impala shell prompt Prompt format: [host:port] db_name> Testing: - Added new shell tests - Ran end-to-end shell tests Change-Id: Ifb0ae58507321e426e5f0f16518671420974a3fc Reviewed-on: http://gerrit.cloudera.org:8080/9927 Reviewed-by: Fredy Wijaya

[09/28] impala git commit: IMPALA-6801: Cleanup request_pool

2018-04-11 Thread tarmstrong
IMPALA-6801: Cleanup request_pool Eliminate the copy of this field in the QuerySchedule. Instead, just set it directly in the TQueryCtx early on. Then, the TQueryCtx doesn't need to be copied by the coordinator. Change-Id: I3bee843ef7d72ba14d487fdb56e55fa3660aafd3 Reviewed-on:

[1/2] impala git commit: Move some test_spilling debug actions to exhaustive

2018-04-11 Thread tarmstrong
Repository: impala Updated Branches: refs/heads/master 242e822ae -> 5bdce5a86 Move some test_spilling debug actions to exhaustive Phil Z pointed out that these tests take a long time to run. Based on experience, we only need the always/never variants to catch the vast majority of

[15/28] impala git commit: IMPALA-6338: Disable flaky bloom filter test

2018-04-11 Thread tarmstrong
IMPALA-6338: Disable flaky bloom filter test The underlying issue in IMPALA-6338 causes successful queries that are cancelled internally due to all results having been returned to, in rare cases, have info missing from the profile. This has caused flaky tests but has low impact on users, and

[25/28] impala git commit: Remove Yarn from minicluster by default.

2018-04-11 Thread tarmstrong
Remove Yarn from minicluster by default. Turns out that we start Yarn as part of the minicluster, but we never use it. (HiveServer2 is configured to run MR jobs "locally" in process.) Likely, this Yarn integration is a vestige of Yarn/Llama integration. We can save memory by not starting it by

[26/28] impala git commit: Revert "Remove Yarn from minicluster by default."

2018-04-11 Thread tarmstrong
Revert "Remove Yarn from minicluster by default." This reverts commit c05df104570fa2cb7067599bbe3b87740ca9f09e. Change-Id: I00151795581d22a9852cceaca1d21325d68dbe59 Reviewed-on: http://gerrit.cloudera.org:8080/9969 Reviewed-by: Philip Zeyliger Tested-by: Philip Zeyliger

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

2018-04-11 Thread tarmstrong
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 hbase-show-create-table.test to show-create-table.test - Ran show-create-table end-to-end tests

[05/28] impala git commit: IMPALA-6779: [DOCS] Improve the REPLICA_PREFERENCE doc

2018-04-11 Thread tarmstrong
IMPALA-6779: [DOCS] Improve the REPLICA_PREFERENCE doc Added detail usage notes for REPLICA_PREFERENCE. Change-Id: If38f9c881f553568c2516ecc23ec501f23ee1f28 Reviewed-on: http://gerrit.cloudera.org:8080/9877 Reviewed-by: John Russell Tested-by: Impala Public Jenkins

impala git commit: IMPALA-6837: allow multiple networks for distcc server

2018-04-11 Thread tarmstrong
Repository: impala Updated Branches: refs/heads/master 54f70b6d6 -> 15b388c5f IMPALA-6837: allow multiple networks for distcc server Testing: Tested the script on Ubuntu 14.04 and CentOS 6 servers to confirm that it resulted in a working configuration. Change-Id:

impala git commit: IMPALA-4631: loosen monotonic clock DCHECK

2018-04-11 Thread tarmstrong
Repository: impala Updated Branches: refs/heads/master 5bdce5a86 -> 54f70b6d6 IMPALA-4631: loosen monotonic clock DCHECK We saw another build failure due to hitting one of these DCHECKs. Let's further loosen the check to avoid the failures on misbehaving systems. Change-Id:

[18/28] impala git commit: Fixing typo in SimpleLogger::Flush()

2018-04-11 Thread tarmstrong
Fixing typo in SimpleLogger::Flush() Change-Id: I5ce0525e8db133f4b1df653b995e3eb108619050 Reviewed-on: http://gerrit.cloudera.org:8080/9893 Reviewed-by: Bharath Vissapragada Tested-by: Impala Public Jenkins Project: