-
Notifications
You must be signed in to change notification settings - Fork 841
[MEDI] Remove collection key type workaround #7010
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
Conversation
src/Libraries/Microsoft.Extensions.DataIngestion/Writers/VectorStoreWriter.cs
Show resolved
Hide resolved
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.
Pull Request Overview
This PR removes a temporary workaround for Qdrant not supporting Guid key types by updating to Semantic Kernel Connectors version 1.67.0-preview, which includes the fix for this limitation.
Key changes:
- Removed the
_keysAreStringsfield and its conditional logic that converted Guid keys to strings for Qdrant - Updated
MicrosoftSemanticKernelConnectorsVersionfrom 1.66.0-preview to 1.67.0-preview
Reviewed Changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| src/Libraries/Microsoft.Extensions.DataIngestion/Writers/VectorStoreWriter.cs | Removed workaround for Qdrant's Guid key limitation by eliminating _keysAreStrings field and using Guid keys directly |
| eng/Versions.props | Updated Semantic Kernel Connectors to version 1.67.0-preview which includes support for Guid keys in Qdrant |
roji
left a comment
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.
👍
This reverts commit a369be9.
Thanks to microsoft/semantic-kernel#13315 the workaround is no longer required.
Microsoft Reviewers: Open in CodeFlow