kudu git commit: error_manager: rename error types

2018-08-28 Thread awong
Repository: kudu Updated Branches: refs/heads/master 2974f5a50 -> 6ec770928 error_manager: rename error types The previous ErrorHandlerType enum names weren't very descriptive, and reflected the expected error handling (e.g. fail a disk, fail a tablet), rather than the error itself. In

[2/3] kudu git commit: KUDU-2469 pt 1: add an IOContext

2018-08-28 Thread awong
http://git-wip-us.apache.org/repos/asf/kudu/blob/2974f5a5/src/kudu/tablet/deltamemstore.h -- diff --git a/src/kudu/tablet/deltamemstore.h b/src/kudu/tablet/deltamemstore.h index b637e00..253a2c9 100644 ---

[1/3] kudu git commit: KUDU-2469 pt 1: add an IOContext

2018-08-28 Thread awong
Repository: kudu Updated Branches: refs/heads/master 846eb7f97 -> 2974f5a50 http://git-wip-us.apache.org/repos/asf/kudu/blob/2974f5a5/src/kudu/tablet/tablet_bootstrap.cc -- diff --git a/src/kudu/tablet/tablet_bootstrap.cc

[3/3] kudu git commit: KUDU-2469 pt 1: add an IOContext

2018-08-28 Thread awong
KUDU-2469 pt 1: add an IOContext This patch introduces the IOContext class that can be used to pass state from the Tablet layer to the CFile layer. The top-level caller (whether it is a Tablet method, an iterator, etc.) will own the IOContext, and pass a pointer to it to lower-level classes. I

[2/2] kudu git commit: KUDU-428: Sentry integration scaffolding

2018-08-28 Thread danburkert
KUDU-428: Sentry integration scaffolding In preparation for KUDU-428 (Sentry integration), this commit introduces some basic module and build-system scaffolding, including a new 'sentry' module, as well as the Sentry service thrift definition files. This is heavily based on the HMS integration

[2/2] kudu git commit: build: different libunwind workaround for 0dc19bfb3

2018-08-28 Thread adar
build: different libunwind workaround for 0dc19bfb3 Rather than add libunwind to the gutil test dependency list twice (once explicitly, and once via KUDU_BASE_LIBS), let's express it as a dependency of glog. That'll cause cmake to adjust the link order based on the new dependency graph, and place

[1/2] kudu git commit: build-support: option to retry all failed tests

2018-08-28 Thread adar
Repository: kudu Updated Branches: refs/heads/master 3bb5f56cf -> d55df3c6e build-support: option to retry all failed tests Currently, users can opt to retry flaky tests as reported by the user-specified test server. The test server's flaky test list may not accurately reflect what tests are