Skip to content

Adding or deleting vector fields is now possible with Qdrant 1.18.0 #53

@graipher

Description

@graipher

scenario

Qdrant 1.18.0 introduced CRUD methods to update existing collections, specifically adding or deleting vector fields: qdrant/qdrant#8605

what does the agent do today?

Current wording: https://github.com/qdrant/skills/blob/main/skills/qdrant-model-migration/SKILL.md

What to Do When Changing Embedding Models

Vectors from different models are incompatible. You cannot mix old and new embeddings in the same vector space. You also cannot add new named vector fields to an existing collection. All named vectors must be defined at collection creation time. Both migration strategies below require creating a new collection.
...

What NOT to Do

  • Assume you can add named vectors to an existing collection (must be defined at creation time)

what should the agent recommend?

The skill should mention the new endpoints, how to use them and the minimum version required for them to exist.

does a related skill already exist?

yes, but it's missing this case

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions