The Kudu team is happy to announce the availability of Kudu 0.7.1. Kudu is currently undergoing Incubation at the Apache Software Foundation.
Kudu 0.7.1 is a bug fix release only for Kudu 0.7.0.
Highlights:
- Notable bug fixes:
- KUDU-1325 fixes a tablet server crash that could occur during table deletion. In some cases, while a table was being deleted, other replicas would attempt to re-replicate tablets to servers that had already processed the deletion. This could trigger a race condition that caused a crash.
- KUDU-1341 fixes a potential data corruption and crash that could happen shortly after tablet server restarts in workloads that repeatedly delete and re-insert rows with the same primary key. In most cases, this corruption affected only a single replica and could be repaired by re-replicating from another.
- KUDU-1343 fixes a bug in the Java client that occurs when a scanner has to scan multiple batches from one tablet and then start scanning from another. In particular, this would affect any scans using the Java client that read large numbers of rows from multi-tablet tables.
- KUDU-1345 fixes a bug where in some cases the hybrid clock could jump backwards, resulting in a crash followed by an inability to restart the affected tablet server.
- KUDU-1360 fixes a bug in the kudu-spark module which prevented reading rows with NULL values.
For a complete list of new features, changes, bug fixes, and known issues, see the Kudu 0.7.1 Release Notes .
As always, your feedback is appreciated. For general Kudu questions, please visit the community page. If you have any questions related to Kudu in Cloudera context, please visit the Cloudera Community Forum.
