Kuzu V0 136

Financial institutions use graph databases to flag circular transactions or sudden connection to known bad actors. With kuzu v0.136, the improved recursive joins allow you to run variable-length pattern matching on the fly. For example:

MATCH (account:Account)-[:TRANSFER*1..4]->(suspicious:Account)
WHERE suspicious.risk_score > 0.8
RETURN account.id, collect(suspicious.id)

The query now completes in under 200ms for graphs with 10 million transactions.

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. kuzu v0 136

Kuzu uses a morsel-driven, vectorized query processor. In v0.1.36, the team focused on specific optimization rules:

result = conn.execute("MATCH (a:Person) RETURN a.name, [ (a)-[:Knows]->(b) | b.name ] AS knows_list") print(result.get_as_data_frame()) Financial institutions use graph databases to flag circular

Kuzu v0.136 is particularly well-suited for:

Less suitable for:

npm install kuzu@0.136.0

If you’re evaluating Kuzu, follow these signs as indicators of maturity: