False. While the fix adds cloning of iterators, the performance regression is <2% for most workloads, and it prevents catastrophic failure. In some recursive path queries, the fix actually improves speed because it eliminates redundant pointer chasing.
# Install specific version
pip install kuzu==0.1.36 # if Python package
All users on earlier v0.136 are strongly advised to upgrade. No changes to the public API or on-disk format – drop-in replacement.
pip install --upgrade kuzu==0.136.fixed # Python example
# or rebuild from source using the `v0.136-fixed` tag
Even with a “fixed” release, a small number of edge cases persist. If you encounter problems after upgrading to kuzu v0.136 fixed, try these solutions: kuzu v0 136 fixed
Issue: “Unknown version number” error on startup
Fix: You likely have a mixed installation. Purge all old libraries: sudo rm -rf /usr/local/lib/kuzu* and reinstall.
Issue: Performance is slower than benchmarks
Fix: The new concurrency model defaults to optimistic locking. If you have extremely high write contention, set kuzu.optimistic_retries = 5 in your config file. For pure read-heavy workloads, enable kuzu.read_only = true. Even with a “fixed” release, a small number
Issue: “Missing symbol: lru_cache_evict”
Fix: You are trying to load a custom plugin compiled against v0.135. Recompile the plugin against the v0.136 headers.
Issue: Migration tool crashes halfway
Fix: Roll back using your backup, then run kuzu dump on v0.135 to export raw data. Install v0.136 fresh and run kuzu load from the dump. This circumvents any on-disk format quirks. Internal discussions also suggest that v0
The stabilization of v0.136 opens the door for new features previously blocked by the underlying instability. The public roadmap for Q3-Q4 includes:
Internal discussions also suggest that v0.136 fixed will serve as the foundation for the v1.0 release candidate scheduled for Q1 next year. The team is now focused on fuzz testing and formal verification of the concurrency layer.
The “fixed” tag in this release is not merely cosmetic. It represents a fundamental overhaul of three major subsystems. Below is a detailed look at the most impactful corrections.
Kuzu v0.1.36 represented a maturation step for the query engine, moving beyond simple graph traversal to include stricter relational constraints. The headline "fix" for this version was the implementation of Foreign Key constraints, a feature highly requested by users attempting to model complex schemas. Additionally, the release included significant upgrades to the LOAD FROM capabilities, closing the gap between Kuzu’s Cypher implementation and standard SQL-like data ingestion.