Kuzu V0: 136 Fixed //top\\

Kùzu continues to bridge the gap between ease of use and high-performance graph computing. With the stability fixes in v0.1.3.6, the team is clearing the path for even more ambitious features in the upcoming v0.2.x series, including deeper integrations with the Arrow ecosystem and further optimizations for GNN (Graph Neural Network) training.

One of the most significant fixes in this version involves memory pressure during large-scale data ingestion. Users previously reported occasional OOM (Out of Memory) errors when importing massive CSV or Parquet files into a graph schema. kuzu v0 136 fixed

Beyond internal fixes, this version improves the stability of the Python and Node.js bindings. The overhead of passing large result sets between the C++ core and the Python layer has been reduced, fixing a latency issue that impacted data scientists using Kùzu for machine learning workflows. Why You Should Upgrade Kùzu continues to bridge the gap between ease

Edge cases in complex Cypher queries—particularly those involving nested WITH clauses and specific aggregations—sometimes led to unexpected "Internal Error" messages. Users previously reported occasional OOM (Out of Memory)

Running on older versions of Kùzu may leave you vulnerable to the specific edge-case crashes addressed in this release. If you are currently on v0.1.2 or an earlier sub-version of v0.1.3, the move to provides a much smoother developer experience with fewer "cryptic" errors during high-load scenarios. How to Update

The parser has been hardened to handle more complex query plans. Specifically, bugs related to how the query optimizer handled certain types of joins in multi-hop queries have been resolved, leading to more predictable execution paths. 3. Concurrency and Thread Safety As an embeddable database, thread safety is paramount.

an existing graph project to Kùzu, or are you starting a fresh implementation with this new version?