The team was devastated. This was not the kind of bug they could afford to ship with. Kenji called an emergency meeting to discuss a plan of action. The bug needed to be squashed, and quickly.
Capable of handling graphs with hundreds of millions of nodes and billions of edges.
Running on older versions of Kùzu may leave you vulnerable to the specific edge-case crashes addressed in this release. If you are currently on v0.1.2 or an earlier sub-version of v0.1.3, the move to provides a much smoother developer experience with fewer "cryptic" errors during high-load scenarios. How to Update
Kùzu v0.13.6 Fixed: Restoring Stability to the Embedded Graph Database Ecosystem
Kùzu v0.1.3.6 introduces more aggressive memory deallocation and better buffer manager coordination during the copy process. This ensures that the system stays within its allocated memory limits even when processing millions of nodes and rels. 2. Cypher Query Parser Refinement kuzu v0 136 fixed
# Install specific version pip install kuzu==0.1.36 # if Python package
: Patched critical JSON NULL parsing errors and rectified structural issues preventing JSON files from streaming correctly via HTTPFS configurations.
Resolved edge cases that could lead to crashes when profiling complex export database commands Transaction Management:
No server setup or maintenance required; runs directly inside your application process. The team was devastated
Note: The "crash" row indicates that previously the workload was impossible. The fixed version enables new query patterns.
people.csv: id,name,age p1,Alice,34 p2,Bob,29
Code 136 on a Chevrolet Cruze (and other GM vehicles) typically indicates a problem with the . This system uses sensors, cameras, and radar to help the driver with parking and obstacle detection.
Fixing issues where null values in large CSV imports caused ingestion crashes. The bug needed to be squashed, and quickly
Kuzu v0.13.6 Fixed! 🚀 The community-driven graph database has rolled out a crucial patch: Kuzu v0.13.6
Columnar disk-based storage with compressed sparse row-based (CSR) adjacency lists.
The vertex scan routine was rewritten to correctly acknowledge the local transaction state, preserving strict serializable ACID transactions. 4. Corrupted Write-Ahead Log (WAL) Recovery
