Add Inspeximus document store integration#554
Open
DanceNitra wants to merge 1 commit into
Open
Conversation
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
|
Someone is attempting to deploy a commit to the deepset Team on Vercel. A member of the Team first needs to authorize it. |
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
1 participant
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.
Adds a Document Store integration page for Inspeximus (MIT, on PyPI as
inspeximus).InspeximusDocumentStoreimplements Haystack'sDocumentStoreprotocol as a drop-in forInMemoryDocumentStore, with two differences that matter for long-running or regulated pipelines: it persists to a file, and itsdelete_documentsremoves the value from disk (with receipts enabled, leaving a signed, content-free tombstone so a deletion is provable).It is a faithful drop-in — the duplicate policies (
SKIP,OVERWRITE,NONE,FAIL) matchInMemoryDocumentStoreexactly (captured from the reference, not guessed), and filtering reuses Haystack's owndocument_matches_filter, soFilterRetrieverand pipeline serialization work unchanged. Parity is verified in CI againstInMemoryDocumentStore, operation by operation, with a falsification control that must fail.The usage example in the page was run end to end against
haystack-ai 3.0.0andinspeximus 1.29.0, and produces the output shown.No logo included for now; happy to add one if you'd like it before merge.
This page was drafted with AI assistance; a human reviewed it and ran the example.