Kuzu V0 136 Fixed ((link)) Official

The Kuzu Project

MATCH (p:Person)-[:ACTED_IN]->(m:Movie) RETURN p.name, COUNT(m) AS movie_count ORDER BY movie_count DESC;

"We can now safely run 6-hop money flow queries. The fix reduced our false positive rate by 18% because we no longer truncate paths due to crashes." kuzu v0 136 fixed

Recent development cycles focused heavily on refining the internal engine and API consistency. Notable fixes included: Crash / regression in [common scenario, e

• Crash / regression in [common scenario, e.g., “executing recursive joins” or “scanning large lists”].
• Memory leak when handling [relevant operation].
• Incorrect results for edge cases involving [e.g., “NULL values in indexed columns”].

• Primary keys are defined in CREATE NODE TABLE for fast lookups.
• Create property indexes if supported in v0.136 for frequent filters (syntax example):

Warning:

If you are currently running v0.135 or earlier, follow these steps to safely upgrade. Due to the concurrency control changes, the on-disk format for transaction logs has changed. While data files remain compatible, pending WAL (Write-Ahead Log) files from v0.135 are not forward-compatible. Primary keys are defined in CREATE NODE TABLE

• @DataEngineerJane (Twitter): “Finally! #Kuzu v0.136 fixed our nightly ETL crashes. Memory usage dropped from 8GB to 1.2GB. The team deserves a raise.”
• Reddit user u/db_fanatic: “I was about to abandon Kuzu for RocksDB. But v0.136 fixed all my pain points. The concurrent writes actually work now. Thank you!”
• Official Kuzu Discord: “No segfaults in 72 hours. That’s a new record for us since v0.135 dropped.”