Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add known vector index issue where queries could be incorrectly rejected #805

Merged
merged 4 commits into from
Dec 20, 2023
Merged

Add known vector index issue where queries could be incorrectly rejected #805

Changes from 1 commit
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
ef19a44
Add known vector index issue where queries could be incorrectly rejected
nilsceberg Nov 30, 2023
41711a4
Update modules/ROOT/pages/indexes-for-vector-search.adoc
JPryce-Aklundh Dec 20, 2023
639ed2b
Update modules/ROOT/pages/indexes-for-vector-search.adoc
JPryce-Aklundh Dec 20, 2023
435cd24
Merge branch 'dev' into dev-vector-index-bug
JPryce-Aklundh Dec 20, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 8 additions & 0 deletions modules/ROOT/pages/indexes-for-vector-search.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -428,6 +428,14 @@ WHERE type = 'VECTOR'
====
| Neo4j 5.15

| Vector indexes may incorrectly reject valid queries in a cluster setting. This is caused by a bug in the handling of index capabilities on followers.
JPryce-Aklundh marked this conversation as resolved.
Show resolved Hide resolved

[TIP]
====
Because index capabilities will be correctly configured on a restart, this issue can be worked around by rolling the cluster after vector index creation.
====
JPryce-Aklundh marked this conversation as resolved.
Show resolved Hide resolved
| Neo4j 5.14

| Querying for a _single_ approximate nearest neighbor from an index would fail a validation check. Passing a `null` value would also provide an unhelpful exception.
| Neo4j 5.13

Expand Down