Kuzu V0 136 [better] «UPDATED»

Kuzu v0.1.36 (released September 2024) is a significant incremental update that solidifies Kuzu’s position as the leading "embeddable" property graph database.

While Kuzu is still pre-version 1.0, it has matured rapidly. Version 0.1.36 is not a rewrite; it is a refinement release that introduces powerful usability features for developers and fixes critical edge cases in query execution. kuzu v0 136

Here is a full review of Kuzu v0.1.36, broken down by features, performance, and usability. Kuzu v0

1. The Headline Feature: COPY FROM Enhancement

The most practical improvement in v0.1.36 is the overhaul of the COPY FROM statement. Kuzu does not have built-in PageRank

  • Previous State: Loading data often required strict formatting or multi-step processes for CSVs/Parquet files.
  • v0.1.36 Update: The engine is now much more robust regarding file parsing. It introduces better support for ignored errors and skips during bulk loading.
  • Verdict: This is a massive quality-of-life improvement. If you are building an ETL pipeline, v0.1.36 is significantly less brittle than previous versions. It reduces the "fiddliness" of getting data into the graph.

Limitations and Roadmap

No tool is perfect. As of kuzu v0.136, the following limitations remain:

  • No distributed mode – You cannot cluster multiple Kuzu instances. It is single-node, though multi-threaded.
  • Graph algorithms library – Unlike Neo4j GDS, Kuzu does not have built-in PageRank, Louvain, or Label Propagation. You must implement these via Cypher iterations.
  • Full-text indexing – Partial support via CONTAINS predicate, but no inverted indices for tokenized search.

The roadmap for v0.140 (planned Q3 2025) includes a built-in procedural language for graph algorithms and a WebAssembly (WASM) build for browser-based graph databases.

4. Cypher Compatibility: UNWIND and CALL {}

Two missing Cypher clauses have been added. The UNWIND clause now works seamlessly with the new LIST type, allowing you to flatten arrays into rows. The CALL {} subquery syntax (with IN TRANSACTIONS) enables batch processing of large updates without overwhelming memory.