Skip to content

chore: Validate vector size during Qdrant -> Qdrant migration#237

Open
Anush008 wants to merge 1 commit intomainfrom
validate-vec-size
Open

chore: Validate vector size during Qdrant -> Qdrant migration#237
Anush008 wants to merge 1 commit intomainfrom
validate-vec-size

Conversation

@Anush008
Copy link
Member

@Anush008 Anush008 commented Mar 3, 2026

No description provided.

Signed-off-by: Anush008 <mail@anush.sh>
@Anush008 Anush008 requested a review from a team as a code owner March 3, 2026 08:10
@Anush008 Anush008 enabled auto-merge (squash) March 3, 2026 12:39
@Anush008 Anush008 disabled auto-merge March 3, 2026 12:39
@Anush008 Anush008 requested review from bashofmann and generall March 3, 2026 14:58

if srcParamsMap != nil {
if tgtParamsMap == nil {
return fmt.Errorf("incompatible collection parameters: source has named vectors config while target does not")
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this might be a valid scenario if we want to add more vectors.
Let's only keep validation for the incorrect dimentions of the same vector for now.

Copy link
Member Author

@Anush008 Anush008 Mar 3, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If a user created a collection with the default unnamed vector, they can add new named vectors?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Also, I propose to keep this check for now.
I'll note to remove this when we support adding new vectors.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants