Fix Qdrant initialization logic when vector size changes #3925
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.
Related GitHub Issue
Closes: #3924
Description
Test Procedure
Type of Change
srcor test files.Pre-Submission Checklist
npm run lint).console.log) has been removed.npm test).mainbranch.npm run changesetif this PR includes user-facing changes or dependency updates.Screenshots / Videos
N/A
Documentation Updates
Important
Fixes Qdrant collection initialization to handle vector size changes by recreating collections and adds tests for this behavior.
qdrant-client.ts.requiresClearlogic fromconfig-manager.tsandmanager.ts.qdrant-client.test.tsto verify collection recreation on vector size change and other scenarios.This description was created by
for 6f87a73. You can customize this summary. It will automatically update as commits are pushed.