Kuzu V0 136 __link__ Page
Released around October 10, 2025, this version introduced several technical refinements to the core engine:
Performance Optimization: Implementation of an 8-byte hash slot for the AggregateHashTable to improve aggregation efficiency.
Storage & Memory Fixes: Resolved issues regarding mmapped memory when spilling to disk and fixed file descriptor leaks for shadow files.
Full-Text Search (FTS): Added support for the ignore_pattern option, allowing for more flexible search indexing.
Language Bindings: Added a Swift package to the Kùzu README, expanding the list of supported client APIs.
CLI Enhancements: The Command Line Interface (CLI) now creates a history file in the home directory for better persistent session management. Getting Started Guide
Since Kùzu is an embedded database, it runs directly in your application process without needing a separate server. Installation Python: pip install kuzu Node.js: npm install kuzu Rust: cargo add kuzu Basic Usage Example (Python)
import kuzu # Create or connect to a database on disk db = kuzu.Database("./my_graph_db") conn = kuzu.Connection(db) # Create a schema (Node table) conn.execute("CREATE NODE TABLE User(name STRING, age INT64, PRIMARY KEY (name))") # Insert data using Cypher conn.execute("CREATE (:User name: 'Alice', age: 30)") # Query the data result = conn.execute("MATCH (u:User) RETURN u.name, u.age") while result.has_next(): print(result.get_next()) Use code with caution. Copied to clipboard Advanced Features kuzu v0 136
Vector Search: Kùzu supports native vector indices for AI and Graph RAG applications.
Interoperability: You can directly ingest data from Parquet or Arrow files.
Extensions: Versions 0.11.3 and later pre-install common extensions like algo, fts (full-text search), json, and vector.
For more detailed tutorials and API references, visit the official Kùzu Documentation or explore their GitHub repository. If you'd like, let me know:
Which programming language you are using (Python, Node.js, Rust, Go, or Swift)?
If you need help with a specific feature (like Full-Text Search or Vector embeddings)? If you are migrating from a different database?
I can provide more tailored code snippets or configuration steps. kuzu - PyPI Released around October 10, 2025, this version introduced
Kùzu v0.13.6: Pushing the Limits of Embedded Graph Analytics The release of Kùzu v0.13.6 continues the momentum of this high-performance, open-source embedded graph database
. Designed for speed and scalability, Kùzu is effectively doing for graph databases what DuckDB did for relational data—providing a lightweight, serverless tool that excels at complex analytical (OLAP) workloads. What is Kùzu? At its core,
is an in-process database written in C++. Unlike traditional graph databases that require a dedicated server, Kùzu runs directly within your application, eliminating the overhead of client-server communication. Key Features of the Kùzu Architecture: Structured Property Graph Model
: It treats nodes and relationships as tables, allowing for columnar storage optimizations usually reserved for relational systems. Cypher Support
: Users can leverage the industry-standard Cypher query language. Vectorized Execution
: It processes data in batches using CPU SIMD instructions, making it significantly faster for multi-hop queries. Novel Join Algorithms
: Kùzu utilizes "worst-case optimal joins" (WCOJ) to handle dense, cyclic graph structures with high efficiency. Enhancements in Recent Versions Kuzu (Japanese: 屑) – means “scrap” or “waste”;
While v0.13.6 specifically focuses on stability and performance refinements, the current release cycle has introduced critical capabilities: Leveraging Kùzu and Cypher for Advanced Data Analysis 24 May 2024 —
5. Known terms similar to “Kuzu”
- Kuzu (Japanese: 屑) – means “scrap” or “waste”; sometimes used in branding or technical slang.
- Kuzu – a surname in Turkey and Japan.
- Kuzu no Honkai – a manga/anime (no version number association).
- Kuzu (software) – There is no widely known open-source project named Kuzu, though search engines may confuse with Kuzu Graph Database (unrelated to v0.136).
Report: Investigation into “kuzu v0 136”
Date: April 11, 2026
Status: Unidentified / No matching reference found
Why This Matters for the Graph Community
The graph database market is often criticized for its complexity. You often need a dedicated DevOps team to maintain a cluster. Kuzu v0.136 represents a maturing vision of "Graph for Everyone."
By focusing on the embedded use case, Kuzu enables:
- Game Developers: To store world states and quest relationships locally without a server.
- Data Scientists: To analyze network graphs directly within a Python script without configuring a Docker container.
- Backend Engineers: To add graph capabilities to their microservices with minimal latency overhead.
Migration Guide: Upgrading to v0.136
If you are currently on a previous version (e.g., v0.120 or v0.130), note the following breaking changes:
- Storage format change: Kuzu v0.136 introduces a new page layout for the buffer manager. Databases created with v0.135 or earlier are not directly readable.
- Solution: Export your data using
COPY TOin the old version, thenCOPY FROMin v0.136.
- Solution: Export your data using
- Function renaming: The
size()function for lists is nowlist_length()(aligned with Cypher standard). - Explicit
COMMIT: Auto-commit on connection close is disabled. You must now callconn.commit()after a write transaction.
A migration script is available in the official documentation: /kuzu/v0.136/upgrade_guide.md