Skip to content

reduce duplicate qdrant api calls in hybrid auto-detect #42

@Goodnight77

Description

@Goodnight77

reduce duplicate qdrant api calls in hybrid auto-detect

problem

when inserting into hybrid collection or dense collection with topology:

  1. _resolve_topology() calls collection_exists() then get_collection() if exists
  2. _ensure_collection() calls get_collection() again to validate dimensions

this means two http round-trips to qdrant for the same collection info every insert.

solution

introduce a unified collection info method that fetches all needed topology and config data in one qdrant api call
both the topology resolution and collection validation use this same result so they don't need separate calls

i can work on this

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions