Repository navigation
v5.3.0 #347
milliondreams
announced in
Announcements
v5.3.0
#347
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
uni-db 5.3.0
Changes since 5.2.1.
5.3.0 makes a search give the same answer before and after a flush. A
filternow holds on unflushed and updated rows in multi-vector search, andsparse search accepts one for the first time. Searches also follow unflushed
label changes and no longer come up short when their best matches have
unflushed updates or deletes. Behaviour and API changes are listed first.
uni.sparse.queryaccepts afilter, and the sparse arm ofuni.searchapplies it (Filtered sparse search: uni.sparse.query rejects the filter and uni.search's sparse arm ignores it #344).
uni.sparse.queryrejected any filter with a "not yetsupported" error (the behaviour 2.4.1 introduced), and
uni.searchpassedits filter to the dense and full-text arms only, so a filtered hybrid search
returned rows the filter excluded. Both now rank only the rows the filter
allows. A caller that relied on the error, or on the sparse arm being
unfiltered, sees different results. The filter is resolved against the
label's table before the sparse index is consulted, so its cost grows with
the number of rows that pass it: a
_vid IN (…)allow-list is cheap, afilter most of a large table passes is not.
pre_filteron the Python OGM'svector_searchandsparse_searchis nowapplied. It was accepted and silently dropped. It is passed to the search
procedure as its filter: a predicate over the label's columns by bare name
(
"age >= 18", not"n.age >= 18"), applied before the top-kcut. A valuewritten in Cypher syntax did nothing before and is an error now.
uni-pydantic5.3.0 requiresuni-db>=5.3.0.uni-storesignatures changed.StorageManager::sparse_searchtakes a
filterand a query context, andSparseVectorIndex::query_topktakes an optional set of allowed vids. Code calling either directly needs
the extra arguments (
Nonekeeps the old behaviour). Theuni-dbfacade isunchanged.
Correctness fixes
uni.vector.queryon aList<Vector>column applied itsfilterto flushedrows only, so an unflushed row outside the filter was returned and could take
a top-
kslot from a row inside it. After such an update was flushed, thesuperseded row version still matched. The filter now applies to unflushed
rows, and only a vertex's latest flushed row can match, with or without a
MUVERA index and on a fork.
krows, or none, whenits best matches had unflushed updates or deletes. Candidates dropped after
the flushed fetch were not replaced. The fetch now widens by the number of
unflushed rows that can displace a flushed hit, as dense search already did.
This did not need a filter to happen.
REMOVE n:Lona flushed vertex, the multi-vector, sparse and full-text searches of
Lstill returned it; after
SET n:L, every search ofL, dense included,missed it. Both lasted until the next flush.
MATCHwas already correct, andthe searches now agree with it.
of them. The 1,000-candidate cap was applied to the flushed and unflushed
candidates together and dropped an arbitrary share of the unflushed ones,
best matches included. It now bounds the flushed candidates only.
Dependencies and build requirements
The requirement stays
>=0.19.2, <1.0.0. What a uni-db user can notice:can fail when the runtime is built: a task the provider does not support,
unchecked
local/onnxand OCR option values, and a modelrevisionthatis a path are now rejected up front instead of failing, or misbehaving,
on first use.
uni-db-cudaanduni-db-metalwheels, each acceleratedlocal/onnxmodel is checked against CPU when it loads. A model whoseaccelerator output disagrees runs on CPU instead of returning wrong
results. Loading costs one extra CPU session and forward pass; set
"accelerator_check": "probe"on an alias for the 0.19 behaviour.graph_optimization_leveland the thread-count options now take effectfor every
local/onnxtask; an alias that set them was silently ignored.published 2026-11-19.
uni-plugin-wasmnow requires>=49.0.6. The fixesmatter to builds that load WebAssembly plugins.
cargo denyignores RUSTSEC-2026-0543 (chrono) and RUSTSEC-2026-0555(
chrono-tz), both "unmaintained" with no patched version. Moving off themchanges the public API and is tracked in chrono is flagged unmaintained (RUSTSEC-2026-0543), failing cargo deny downstream #341. A crate that depends on
uni-db and runs
cargo denywith the default policy needs the same ignores.libsais-rs0.2.2 → 0.2.4 andclipboard-win5.4.1 → 5.4.3 in the lockfile;the older versions were yanked.
This discussion was created from the release v5.3.0.
All reactions