Welcome to the seventeenth edition of the Kudu Weekly Update. This weekly blog post covers ongoing development and news in the Apache Kudu (incubating) project.
Development discussions and code in progress
-
Dan Burkert has continued making progress on support for non-covering range partitioned tables. This past week, he posted a code review for adding and dropping range partitions to the master and another for handling non-covering ranges in the C++ client.
-
Adar Dembo continued working on addressing multi-master issues, as he explained in this blog post. This past week he worked on tackling various race conditions that were possible when master operations were submitted concurrent with a master leader election.
Adar also posted patches for most of the remaining known server-side issues, including posting a comprehensive stress test which issues client DDL operations concurrent with triggering master crashes and associated failovers.
As always, Adar’s commit messages are instructive and fun reads for those interested in following along.
- As mentioned last week, David Alves has been making a lot of progress on the implementation
of the replay cache. Many patches landed in master this week, including:
Currently, this new feature is disabled by default, as the support for evicting elements from the cache is not yet complete. This last missing feature is now up for review.
- Alexey Serbin has been working on adding Doxygen-based documentation for the public C++ API. This was originally proposed on the mailing list a couple of weeks ago, and last week, Alexey posted the initial draft of the implementation.
Project news
- The discussion on the dev mailing list about having an intermediate release, called 0.10.0, before 1.0.0, has wound down. The consensus seems to be that the development team is in favor of this release. Accordingly, the version number in the master branch has been changed back to 0.10.0-SNAPSHOT.
Want to learn more about a specific topic from this blog post? Shoot an email to the kudu-user mailing list or tweet at @ApacheKudu. Similarly, if you’re aware of some Kudu news we missed, let us know so we can cover it in a future post.