Archives
Categories
Meta

The Kùzu v0.3.6 update significantly strengthens the database's reliability and internal handling of complex data structures. This release focuses on "fixing the plumbing," resolving critical edge cases in transactions, and refining the system's ability to handle advanced union types and full-text search. Key Technical Improvements Robustness & Integrity:

Check the Issue Tracker: Search for the specific bug behavior you are seeing.

  • Native ARM64 support (Apple Silicon and AWS Graviton). Currently, Kuzu runs via Rosetta 2; native builds are in alpha.
  • Pluggable storage backends: S3-compatible object storage as a tiered cache.
  • Graph query language extension: A Cypher-like syntax for connected data, leveraging the new concurrency model.
  • WebAssembly (WASM) build: Run Kuzu directly in the browser, with indexedDB persistence.

Could you clarify where you saw the "v0.136" reference?It's possible it refers to: A specific commit hash (though usually longer).

Upgrade Recommendation: If you are on a version prior to 0.1.36, upgrading is strongly recommended to take advantage of the new REFERENCES constraint syntax, which prevents data corruption in graph relationships.

The kuzu v0.136 fixed release is not just a patch; it is a re-foundation. The three critical memory and concurrency bugs have been eradicated, performance has exceeded pre-regression levels, and the upgrade path is smooth for the vast majority of users. For any team currently stuck on v0.134 or suffering through v0.135, this update is mandatory.

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.

4. Memory Management in Pipelines

The release included under-the-hood fixes for the pipelined query execution engine.

  • Unclear scope: which project (kuzu) and what component changed?
  • Ambiguous versioning: "v0 136" is confusing — is it "v0.136", "v0.1.36", or something else?
  • Vague verb: "fixed" doesn’t state what bug/issue was fixed.
  • No reference: missing issue/PR number, file(s), or tests.