fix(milvus): Fix upsert operations when autoId is false #8501
Conversation
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
When autoId is set to false, the primary field was being incorrectly removed from the fields array during collection initialization, causing upsert operations to fail and documents to be added instead of updated. The issue was in grabCollectionFields() where fields with autoID: true were being removed regardless of the user's autoId setting. This fix ensures that autoID fields are only removed when both the field has autoID: true AND the user has set autoId: true. Changes: - Modified field removal logic in grabCollectionFields() to check both field.autoID and this.autoId before removing fields - Added comprehensive unit tests covering various autoId scenarios - Tests verify primary field handling, document processing, and error cases Fixes upsert functionality when users provide their own document IDs through metadata with autoId: false.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
1 Skipped Deployment
|
hntrl
approved these changes
Aug 15, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Description
This PR fixes a bug in the Milvus vector store implementation where upsert operations would fail when
autoIdis set tofalse. The issue was that the primary field was being incorrectly removed from the fields array during collection initialization, causing documents to be added instead of updated during upsert operations.Root Cause
The bug was in the
grabCollectionFields()method where fields withautoID: truewere being removed fromthis.fieldsregardless of the user'sautoIdsetting. This caused the primary field to be missing during document processing in theaddVectors()method, making upsert operations fail.Solution
Modified the field removal logic in
grabCollectionFields()to only remove autoID fields when both conditions are true:field.autoIDis true (database schema property)this.autoIdis true (user's preference)This ensures that when
autoId: false, the primary field remains inthis.fieldsand gets processed correctly for upsert operations.Testing
Added comprehensive unit tests covering:
autoIdsettingNote for reviewers: The unit tests will show harmless error logs during execution due to the MilvusClient constructor attempting connections during instantiation. This is expected behavior and doesn't affect test validity. The tests use a
TestMilvusclass that extends the main class to expose internal methods for testing without requiring network connections. Consider migrating to Vitest for better ESM mocking capabilities in the future.Fixes #8495