Add incremental search index appends - #3
Draft
lee101 wants to merge 1 commit into
Draft
Conversation
|
Codex Infinity Start a task on this PR's branch by commenting:
Tasks and logs: https://codex-infinity.com |
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 strict incremental append APIs for one or more caller-supplied document IDs.
This lets high-load consumers add freshly generated assets without rebuilding and re-embedding the complete index. Duplicate IDs are rejected before mutation, concurrent calls serialize through the existing engine lock, and single-item batches now start only one embedding worker.
Root cause: consumers had no explicit insert-only API and used full index reconstruction to preserve ID-to-document consistency.
Validation:
go test -race . -run TestSearchEngineAppend -count=1