Skip to content

Fix empty sparse vector name validation#8194

Merged
timvisee merged 2 commits into
qdrant:devfrom
leohenon:fix/sparse-empty-vector-name-5209
Apr 10, 2026
Merged

Fix empty sparse vector name validation#8194
timvisee merged 2 commits into
qdrant:devfrom
leohenon:fix/sparse-empty-vector-name-5209

Conversation

@leohenon
Copy link
Copy Markdown
Contributor

@leohenon leohenon commented Feb 22, 2026

Fixes #5209.

Block empty sparse vector names on collection creation.
Adds a regression test.
Does not migrate existing invalid configs.

Copilot AI review requested due to automatic review settings February 22, 2026 11:38

This comment was marked as resolved.

coderabbitai[bot]

This comment was marked as resolved.

@qdrant qdrant deleted a comment from coderabbitai Bot Apr 10, 2026
Copy link
Copy Markdown
Member

@timvisee timvisee left a comment

Choose a reason for hiding this comment

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

Thanks!

Normally I'd consider this as breaking change since we're enforcing extra limits here. But I see behavior with this vector name was broken before anyway, which makes it reasonable to expect nobody is using it like this.

Here's a place we enforce this already:

debug_assert!(false, "Sparse vector cannot be default");

In documentation we also state this:

Unlike dense vectors, sparse vectors must be named.

https://qdrant.tech/documentation/manage-data/collections/#collection-with-sparse-vectors

Thank you for the test as well.

@timvisee timvisee merged commit b8a78c1 into qdrant:dev Apr 10, 2026
15 checks passed
@leohenon leohenon deleted the fix/sparse-empty-vector-name-5209 branch April 10, 2026 11:31
timvisee pushed a commit that referenced this pull request May 8, 2026
* Fix empty sparse vector name validation

* Reorder validation to check empty sparse name before duplicate name

---------

Co-authored-by: leohenon <[email protected]>
@timvisee timvisee mentioned this pull request May 8, 2026
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.

3 participants