Repository navigation
[diskann-garnet] Split finish_import into finish_import and verify_im… - #1515
Merged
Merged
Conversation
Jack Moffitt (metajack)
requested review from
a team
and
a balanced review from Copilot
October 26, 2026 22:09
Contributor
There was a problem hiding this comment.
🟡 Changes recommended
Concurrent finish_import calls can overwrite the cache with stale start-point neighbors after an insertion, leaving searches with outdated graph links while still reporting success.
1 open issue
What changed in this PR
This PR separates import verification from finalization in the Garnet integration, allowing trusted importers and replicas to skip verification and simplifying replication sequencing.
Changes:
- Introduces optional partitioned
verify_importand a standalone Boolean-returningfinish_import. - Updates import tests and documentation, and rejects mismatched callback read lengths.
- Bumps the Garnet package to version 9.0.0 for the changed FFI.
| File | Description |
|---|---|
diskann-garnet/src/provider.rs |
Separates verification from finalization and updates provider tests. |
diskann-garnet/src/lib.rs |
Exposes the separate verification and finalization FFI functions. |
diskann-garnet/src/garnet.rs |
Checks read lengths before copying callback data. |
diskann-garnet/src/ffi_tests.rs |
Tests separate verification and finalization paths. |
diskann-garnet/src/dyn_index.rs |
Updates dynamic index methods for the split API. |
diskann-garnet/README.md |
Explains the revised import workflow. |
diskann-garnet/docs/ffi-design.rs |
Documents the new FFI signatures and contracts. |
diskann-garnet/docs/data-design.md |
Clarifies import status transitions and start-point handling. |
diskann-garnet/diskann-garnet.nuspec |
Bumps the NuGet package to 9.0.0. |
diskann-garnet/Cargo.toml |
Bumps the Rust crate to 9.0.0. |
Cargo.lock |
Records the updated crate version. |
Review effort: Balanced
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #1515 +/- ##
==========================================
+ Coverage 92.16% 92.19% +0.03%
==========================================
Files 592 592
Lines 123582 123638 +56
==========================================
+ Hits 113899 113988 +89
+ Misses 9683 9650 -33
Flags with carried forward coverage won't be shown. Click here to find out more.
🚀 New features to boost your workflow:
|
Jack Moffitt (metajack)
force-pushed
the
push-oyvypkvrrmqy
branch
from
October 27, 2026 14:28
b5d6a8d to
7f54503
Compare
Jack Moffitt (metajack)
force-pushed
the
push-oyvypkvrrmqy
branch
from
October 27, 2026 16:02
7f54503 to
064e1b8
Compare
Mark Hildebrand (hildebrandmw)
approved these changes
Oct 28, 2026
Harsha Simhadri (harsha-simhadri)
approved these changes
Oct 30, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.

This decouples index verification from finalization. This is beneficial to skip when the importer is trusted to be correct, and because the replicas do not need to do this extra work anyway. This has an added benefit of making sequencing of these commands during replication much easier to deal with.