[1/2] kudu git commit: [java] Reuse snapshot scan timestamp across tablets

Repository: kudu Updated Branches: refs/heads/master 1a0099f91 -> 2f1a2a06d [java] Reuse snapshot scan timestamp across tablets KUDU-1189 On reads at a snapshot that touch multiple tablets, without the user setting a timestamp, use the timestamp from the first server for following scans. For

[2/2] kudu git commit: [java] KUDU-1679 Propagate timestamps for scans

[java] KUDU-1679 Propagate timestamps for scans This is Java counterpart for 06bb52d2acc6d311144aa905101ec5d846096611. Change-Id: I84d45ba395f2a3fc6b54591f4a45bb4f10435910 Reviewed-on: http://gerrit.cloudera.org:8080/5248 Reviewed-by: David Ribeiro Alves Tested-by: Kudu

kudu git commit: Fix bitshuffle arch-wrapper code to build on OSX

Repository: kudu Updated Branches: refs/heads/master 88755e98d -> 1a0099f91 Fix bitshuffle arch-wrapper code to build on OSX OSX doesn't have objcopy, so we don't have the avx2 symbols available. This hard-codes the non-AVX2 symbol usage on OSX. Change-Id:

kudu git commit: KUDU-1448 (take 2). Enable AVX2 bitshuffle at runtime

Repository: kudu Updated Branches: refs/heads/master 04eeacddd -> 88755e98d KUDU-1448 (take 2). Enable AVX2 bitshuffle at runtime This uses some trickery when building bitshuffle so that we build it twice: once with normal flags and a second time with -mavx2. Enabling AVX2 turns on some

[1/6] kudu git commit: Reduce the number of batches in FuzzTest::TestFuzzHugeBatches

Repository: kudu Updated Branches: refs/heads/master dad80bd50 -> 04eeacddd Reduce the number of batches in FuzzTest::TestFuzzHugeBatches While running fuzz-itest in dist-test with slow mode, asan, it's often flaky due to timeouts. This test is the main culprit as it often takes 13 minutes to

[4/6] kudu git commit: Note to install "which" command in the installation guide in case of building on RHEL/CentOS.

Note to install "which" command in the installation guide in case of building on RHEL/CentOS. I tried to build on Docker container with official CentOS7 image and when I tried to build thirdparty libraries, I caught an error message as follows. + /root/work/kudu/thirdparty/preflight.py

[4/6] kudu git commit: Change TabletHistoryGCITest back to manual flushes

Change TabletHistoryGCITest back to manual flushes Mike found a potential problem with client flushes when there are concurrent manual and automatic flushes going on (KUDU-1761). Until we address that this changes this test back to MANUAL_FLUSH with a single flush at the end of each batch. This

[6/6] kudu git commit: [java-client]: support for Kerberized RPC

[java-client]: support for Kerberized RPC This commit adds initial support for connecting to a Kerberized cluster with the Java client. The application is required to have an active login context which contains a subject with Kerberos credentials when creating the KuduClient to connect to a

[2/6] kudu git commit: Allow to skip the scan part of full_stack-insert-scan-test

Allow to skip the scan part of full_stack-insert-scan-test This test is good to microbenchmark/run perf on writes but the scan part of the test introduces noise in this case. This patch adds a flag to allow to skip the scan part of the test. Change-Id: I93e4c0dd5637bb8992f5f2fd51d4f3811e468974

[5/6] kudu git commit: c++11'ize CompactionInput descedants with 'override'

c++11'ize CompactionInput descedants with 'override' Change-Id: I9dd25733f0f33ff824b854cb4f31b4a5d973a685 Reviewed-on: http://gerrit.cloudera.org:8080/5227 Tested-by: Kudu Jenkins Reviewed-by: Alexey Serbin Reviewed-by: Todd Lipcon Project:

[1/6] kudu git commit: Remove suppression for already-fixed KUDU-189

Repository: kudu Updated Branches: refs/heads/master 11fa20723 -> dad80bd50 Remove suppression for already-fixed KUDU-189 The code mentioned in this suppression was removed in July 2014 by 0c440b0253e97209c6481608e941e6532db3bd20 Change-Id: I8cd3b917a25cb6d0de7e04d26087cf249f5d00d0