: The addition of fsync() on WAL (Write-Ahead Logging) and fullfsync specifically for macOS/iOS enhances crash recovery and prevents data corruption.
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
: Fixed a severe structural bug where subqueries inside COPY FROM statements would trigger type mismatches during multi-stage data ingestion pipelines.
One of Kùzu's standout features is its seamless integration with the modern data stack, allowing zero-copy data transfers via Apache Arrow and direct querying from DuckDB. This release irons out minor type-mapping discrepancies between Arrow data types and Kùzu’s internal logical types, specifically improving the handling of timestamp zones and nullability constraints. Performance Impact: What Users Can Expect
With v0.136 , this functionality has been and moved to a dedicated, standalone extension: djc-ext-pydantic . kuzu v0 136 fixed
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 search for "kuzu v0 136 fixed" is a perfect example of how the same code can mean very different things. For a data engineer, it means trying to solve a specific versioning bug in an emerging graph database. For a car owner, it means trying to reset their car's computer to get their parking sensors working again.
Reduced memory footprint and faster execution times for complex, deeply nested queries. 3. Enhanced Vector and Full-Text Search Stability
Employs columnar disk-based storage and vectorized execution for extremely fast multi-hop queries. Recent Critical Fixes & Improvements : The addition of fsync() on WAL (Write-Ahead
Kuzu’s development trajectory remains focused on bridging structured analytical queries with unstructured machine learning workflows. Feature Category Capability v0.13.6 Impact & Fixes Single-file storage footprint
Fixing issues where null values in large CSV imports caused ingestion crashes.
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.
The improvements implemented in the v0.13.6 codebase established a clear structural divergence from previous legacy iterations: Feature/Metric Legacy Kùzu Versions Kùzu v0.13.6 (Fixed & Optimized) Restricted precision Native DOUBLE precision columns In-Memory HNSW Uncompressed node indexing Compressed neighbor offsets Match Clauses Sequential, independent scans Merged consecutive MATCH logic Data Ingestion Prone to COPY FROM subquery bugs Safe, type-checked subquery streaming Buffer Management Unoptimized individual evictions Batch-processed eviction candidates The Legacy of Kùzu v0.13.6 Corrupted Write-Ahead Log (WAL) Recovery : Fixed a
This public link is valid for 7 days and shares a thread, including any personal information you added. This link or copies made by others cannot be deleted. If you share with third parties, their policies apply. Can’t copy the link right now. Try again later. Releases · kuzudb/kuzu - GitHub
: Fixed an OS-specific path parsing error on Windows that previously disrupted local database importing routines. Performance Enhancements & Graph RAG Optimization
If you are experiencing bugs in an older version, the "fix" is almost always to upgrade to the latest stable build. pip install kuzu --upgrade Use code with caution. Copied to clipboard Using Node.js: npm install kuzu@latest Use code with caution. Copied to clipboard 3. Key Areas Addressed in Recent "Fix" Cycles
Short, conventional commit (if fixing a specific bug) kuzu: fix crash in query planner when handling empty projections (or) kuzu(v0.1.36): fix planner crash on empty projection