Kuzu V0: 136 Fixed

Most users report a seamless upgrade taking under 90 seconds. A small subset using custom compiled extensions may need to rebuild those modules against the new v0.136 ABI.

Kuzu v0.1.36 was not merely a "bug fix" patch; it was a structural update that hardened the database's relational capabilities. By implementing Foreign Keys and refining the data ingestion pipeline, Kuzu solidified its position as a robust solution for applications requiring the flexibility of Cypher with the data integrity of traditional RDBMS systems.

Upgrade Recommendation: If you are on a version prior to 0.1.36, upgrading is strongly recommended to take advantage of the new REFERENCES constraint syntax, which prevents data corruption in graph relationships.

Kùzu is an in-process, embedded property graph database designed for speed and scalability. While the project has been archived as of late 2025, recent releases—specifically leading up to and including v0.1.3.6—focused on critical stability fixes and advanced query capabilities. Key Technical Improvements

The v0.1.3.x development cycle addressed several core architectural issues to improve performance in analytical workloads: Transaction and Persistence Fixes:

WAL Syncing: Implementation of fsync() on Write-Ahead Logs (WAL) during database opening and fullfsync support specifically for macOS/iOS to prevent data corruption.

Recovery Stabilization: Fixed issues where the system would attempt to recover twice from a corrupted WAL. Query Processor Stability:

Nested Unions: Fixed bugs related to casting between unions and handling issues with nested unions and union lists/arrays. kuzu v0 136 fixed

Vertex Scans: Resolved issues with OnDiskGraph vertex scans occurring during active transactions.

Detach Delete: Fixed "detach delete" operations within the local relationship table. Search & Performance:

FTS Wildcards: Added support for wildcard patterns in Full-Text Search (FTS) queries and implemented FTS updates.

Caching: Introduced caching for prepared statements in the client context to reduce query overhead.

Concurrency: Added locks to the local hash index and established basic concurrent insertion tests for better multi-core safety. Core Database Features

Despite its archived status, Kùzu remains a powerful tool for Graph RAG and hybrid search workflows: Description Storage Engine

Columnar disk-based storage with compressed sparse row-based (CSR) adjacency lists. Query Language Most users report a seamless upgrade taking under 90 seconds

Uses the openCypher query language, familiar to Neo4j users. Integration

Embedded (in-process) like DuckDB, requiring no server setup. Scalability

Capable of handling graphs with hundreds of millions of nodes and billions of edges. AI Workloads

Native support for vector indices (since v0.10.0) for fuzzy search and vector-assisted graph traversal.

For those looking for an actively maintained alternative following Kùzu's archiving, FalkorDB or Neo4j are recommended by community members. kuzudb/kuzu: Embedded property graph database ... - GitHub

To quantify the impact of kuzu v0.136 fixed, we ran a series of benchmarks on a standard Ubuntu 22.04 instance (16GB RAM, 4 vCPUs) using the LDBC Social Network Benchmark (SF 0.1).

| Workload Type | v0.136 (Broken) | v0.136 (Fixed) | Improvement | |---------------|----------------|----------------|-------------| | 2-hop friends | 124 ms (unstable) | 118 ms | +5% stability | | 5-hop path query | Crash (100%) | 1,420 ms | Infinite | | Bulk insert (1M edges) | 8.2 sec (leaky) | 7.9 sec | +3.7% | | Memory peak (10 concurrent queries) | 2.4 GB (fragmented) | 1.9 GB | -21% | Upgrade Recommendation: If you are on a version prior to 0

Note: The "crash" row indicates that previously the workload was impossible. The fixed version enables new query patterns.

In a small, innovative tech firm nestled in the heart of Tokyo, a team of developers worked tirelessly on "Kuzu," an ambitious open-source project aimed at redefining how data was interacted with across different platforms. Kuzu was designed to be a highly efficient, scalable graph database, capable of handling complex queries with ease, something the team believed would be a game-changer for developers worldwide.

The project was led by Kenji, a meticulous and passionate developer with a vision for Kuzu to become a household name in the tech community. His team was a diverse group of young talent, each bringing their unique skills and perspectives to the table.

If you are currently running the broken v0.136, do not simply rebuild from source. Follow this verified migration path:

The community flagged this as Issue #1124 on the official Kuzu GitHub repository. The maintainers acknowledged the severity within 48 hours, labeling it “P1 - Breaking.”

The team worked through the night, poring over lines of code, testing patches, and stressing the system to find where it was breaking. It wasn't easy; several proposed fixes introduced new issues or broke existing functionality.

However, there was one member of the team, a quiet but incredibly skilled developer named Yui, who had a knack for understanding complex systems. She took a step back, re-read the documentation and issue reports, and then suggested a novel approach to solving the bug. Her solution involved not just fixing the immediate cause but also implementing additional checks to prevent similar issues in the future.