[2/2] kudu git commit: KUDU-721: [Python] Add DECIMAL column type support

KUDU-721: [Python] Add DECIMAL column type support This patch adds basic support to the Python client to create, read, and write tables with DECIMAL columns. Change-Id: I8e0855100ab1ea891f990931ec94d0b98c0dece1 Reviewed-on: http://gerrit.cloudera.org:8080/9496 Tested-by: Kudu Jenkins

[1/3] kudu git commit: KUDU-2297 (part 3): refactor process-wide stack collection out of /stacks

Repository: kudu Updated Branches: refs/heads/master 416b3018a -> 00815045f KUDU-2297 (part 3): refactor process-wide stack collection out of /stacks Previously a bunch of logic to collect all the stacks from the process was in the /stacks path handler. This logic is relatively generic and

[2/3] kudu git commit: KUDU-2297 (part 4): periodically dump stacks to diagnostics log

KUDU-2297 (part 4): periodically dump stacks to diagnostics log This modifies the diagnostics log to periodically dump stack traces. This is slightly complicated by the fact that symbolized stack traces can be relatively large. So, we separate the logging of symbols and stack traces. When an

[3/3] kudu git commit: Don't perform compactions when clean time has not been advanced

Don't perform compactions when clean time has not been advanced Due to KUDU-2233 we might not advance safe time, and thus clean time, at bootstrap causing possible corruption or crashes. This patch adds a check to make sure that clean time has been advanced at all before performing a compaction.

[1/2] kudu-site git commit: Publish commit(s) from site source repo: b63f40d Kudu Consistency Blog Post Pt1

Repository: kudu-site Updated Branches: refs/heads/asf-site 3de2c02bd -> 0631d4dbb http://git-wip-us.apache.org/repos/asf/kudu-site/blob/0631d4db/blog/page/2/index.html -- diff --git a/blog/page/2/index.html

kudu git commit: Kudu Consistency Blog Post Pt1

Repository: kudu Updated Branches: refs/heads/gh-pages cab08ebf1 -> b63f40d13 Kudu Consistency Blog Post Pt1 This is the first part of multi-part blog post series about consistency in Kudu. It's hard to talk about consistency topics without context, particularly in blog posts where we can't

kudu git commit: KUDU-2083. Decrement running maintenance ops on failed prepare

Repository: kudu Updated Branches: refs/heads/master 31ddbcf0b -> b365ad0bd KUDU-2083. Decrement running maintenance ops on failed prepare There is currently a bug where we don't decrement the number of running ops when an op->Prepare() fails. Although rare, when this bug is hit, it will

kudu git commit: Fix SIGSEGV in ksck

Repository: kudu Updated Branches: refs/heads/master d62394293 -> def06d8b8 Fix SIGSEGV in ksck ksck will segfault when some tablet servers that host tablet replicas are missing. This happens, for example, if the master is still restarting and has not yet fully populated its list of live

kudu git commit: log-rolling-itest: delete test files when test ends

Repository: kudu Updated Branches: refs/heads/master 10aeb2877 -> 0c1b52fdf log-rolling-itest: delete test files when test ends By not inheriting from the KuduTest fixture, this test didn't clean up after itself. Normally this is caught in build-and-test.sh by the TEST_TMPDIR contents check,

[1/2] kudu git commit: KUDU-1952 Remove round-robin for block placement

Repository: kudu Updated Branches: refs/heads/master ce83b6cef -> 732ee211a http://git-wip-us.apache.org/repos/asf/kudu/blob/732ee211/src/kudu/fs/log_block_manager.cc -- diff --git a/src/kudu/fs/log_block_manager.cc

[2/2] kudu git commit: KUDU-1952 Remove round-robin for block placement

KUDU-1952 Remove round-robin for block placement This is the first of a multi-patch patchset to mitigate the effects of single-disk failure. Throughout the code, the term "DataDir" refers to a data directory, which is often mounted on a distinct disk. Thus, "disks" and "data directories" will be

kudu git commit: [flaky tests] Address LSAN false positives

Repository: kudu Updated Branches: refs/heads/master 174a058e2 -> dcd029eca [flaky tests] Address LSAN false positives Some tests, like external_mini_cluster-itest, are now only failing in ASAN due to leaks. Upon inspection I could only find false positives among these leaks around thread

kudu git commit: Expose row format flags in KuduScanner

Repository: kudu Updated Branches: refs/heads/master 899e6a5e5 -> 75333640b Expose row format flags in KuduScanner This adds a way to pass row format modifier flags to KuduScanner, encoded in an int64_t as a bitset. This API is marked as advanced and it's explicitely called out that the user

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-site git commit: Publish commit(s) from site source repo: a37d733 Fix list rendering of the last weekly update post

Repository: kudu-site Updated Branches: refs/heads/asf-site c5db00e9b -> 20ae141f4 Publish commit(s) from site source repo: a37d733 Fix list rendering of the last weekly update post Site-Repo-Commit: a37d733b3caf1bfc9b172002de4c651566dac8dc Project:

kudu git commit: Fix list rendering of the last weekly update post

Repository: kudu Updated Branches: refs/heads/gh-pages 4f12e1baa -> a37d733b3 Fix list rendering of the last weekly update post The sublist after "Noteworthy features/improvements" is not rendering properly. Apparently it was missing a new line to be indentified as a list but adding it made

[1/2] kudu git commit: [tests] MANUAL_FLUSH --> AUTO_FLUSH_BACKGROUND

Repository: kudu Updated Branches: refs/heads/master 7327c28b2 -> 80923d690 [tests] MANUAL_FLUSH --> AUTO_FLUSH_BACKGROUND In tests, run KuduSession in AUTO_FLUSH_BACKGROUND instead of MANUAL_FLUSH mode where appropriate. Change-Id: Ieafc198609cceb5d6945a910364056d81786629a Reviewed-on:

[2/2] kudu git commit: Patch gperftools to be able to work on macOS Sierra/XCode 8

Patch gperftools to be able to work on macOS Sierra/XCode 8 Apparently gperftools needs to be patched for tcmalloc to work with the new clang version that ships with XCode 8, but the fix hasn't landed yet. This patch fixes that and was copied verbatim from: