Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
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 some basic HNSW graph checks to CheckIndex #13984
base: main
Are you sure you want to change the base?
Add some basic HNSW graph checks to CheckIndex #13984
Changes from 7 commits
9dd11ed
b16c84d
bc819a8
2b0f06a
4da69e8
1962b81
49bae88
31e0d18
8d78d02
0bbfd55
37ed6d7
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hmm the field can be anything (not necessarily
knn
likeluceneutil
uses)? Can we change this so we iterateFieldInfos
and for any field that has KNN vectors enabled (FieldInfo.hasVectorValues
, hmm but also has the HNSW graph (since I think a field can be only "flat" vectors?)) we do this check?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks, I didn't quite understand fields when I wrote this - I think I get it now. Alright, I've done what you suggested (as is also done in
testVectors
) and iterated overFieldInfos
, performing the check only when it applies.Because we might now parse several HNSW graphs, I've restructured the status object to support per-graph data. Successful output will now look like:
testVectors
doesn't do this, it just sums vectors over all fields. I could do that too, but this felt most complete.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Instead of incrementing here, you could just set it to
numLevels
from above?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I could, but wanted to respect the object as a "status" - so if a check fails,
numLevels
will indicate on which level it failed. However we don't print the status if an exception is thrown. What do you think?