If you saw "v0.136" in a specific repository or community thread, it might be an internal build or a community fork. The official releases can always be verified on the Kùzu GitHub Releases page . v0.7.1 (Latest as of early 2024).
As an ACID-compliant database, Kùzu uses a Write-Ahead Log to guarantee data integrity during unexpected application crashes. Under heavy, concurrent read-write workloads, race conditions could occasionally cause the WAL checkpoints to stall. kuzu v0 136 fixed
An iterator exhaustion bug affecting QueryResult processing loops has been permanently fixed, preventing thread-blocking scenarios when mapping query outputs into custom application structs. If you saw "v0
: Data type mapping—specifically handling complex nested lists, structs, and high-precision timestamps passed from Python (Pandas/Arrow) or JavaScript—is now seamless. Arrow-based data ingestion pipelines will experience fewer serialization bottlenecks. Performance Enhancements As an ACID-compliant database, Kùzu uses a Write-Ahead
, a popular open-source tool used primarily for managing and executing scripts in the gaming environment.
;
To understand why the bug fixes in v0.13.6 are critical, it is essential to trace how Kùzu manages highly connected datasets inside a single node system. Unlike traditional operational graph databases that rely on pointer chasing over row-oriented records, Kùzu integrates structural innovations to speed up OLAP style graph traversal: