As an MIT-licensed, in-process graph database designed for query speed and scalability, Kùzu continues to gain traction among data scientists and engineers who need Cypher-query capabilities without the overhead of a client-server architecture. Kùzu v0.13.6 delivers essential fixes that prevent runtime panics and ensure deterministic query outcomes under heavy analytical workloads. What is Kùzu? A Brief Overview
Resolving race conditions when multiple read-only connections access the database simultaneously.
The release is not a full version upgrade to v0.137. Instead, it is a targeted hotfix applied on top of the v0.136 codebase. The patch focuses on three specific areas:
The "fixed" aspect of version 0.1.3.6 focuses on three main pillars: , Cypher Parser Robustness , and Storage Layer Consistency . 1. Improved Memory Handling during Bulk Loads kuzu v0 136 fixed
Version 0.135 broke support for nested JSON objects exceeding three levels. Developers relying on Kuzu’s built-in JSON extractor received malformed outputs or outright segfaults. This was particularly painful for those using Kuzu as an ETL (Extract, Transform, Load) tool.
! This release directly addresses critical bugs and optimizes stability, ensuring your analytical property graph workloads run smoother than ever.
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: As an MIT-licensed, in-process graph database designed for
Specific to multi-threaded queries involving path-finding (e.g., variable-length relationships), v0.1.36 optimized memory buffer reuse. This fixed out-of-memory (OOM) errors encountered when running breadth-first searches over dense graphs with high cardinality.
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).
The phrase "kuzu v0.1.3.6 fixed" refers to a specific update or patch for A Brief Overview Resolving race conditions when multiple
The refinements to the vectorized engine mean faster query results.
🚀 Kuzu v0.136 is fixed! The patch resolves the recursive CTE memory leak and MATCH path timeouts from the initial release.