muscles-data-qdrant
Qdrant adapter package for muscles-data.
This package is intentionally separate from muscles-data: the core package
owns typed ports, resource runtime and diagnostics, while this package owns the
Qdrant-backed VectorSearchPort implementation.
Related packages
- Core runtime and port contracts:
muscles-data - Elasticsearch search adapter:
muscles-data-elasticsearch - OpenSearch search adapter:
muscles-data-opensearch - Redis key-value/lock/stream adapter:
muscles-data-redis - MongoDB document-store adapter:
muscles-data-mongodb - S3 object-store adapter:
muscles-data-s3 - SQLAlchemy direct SQL resource adapter:
muscles-data-sqlalchemy - Executable example:
example_data_qdrant_1
Usage
Register this adapter once in the application composition root when building
the shared DataAdapterCatalog, alongside other configured adapters:
catalog.register(QdrantVectorFactory())
The vector.docs resource itself is declared in the application's central
data.resources configuration shown below. A package resolves the port from
the existing runtime; it does not build another catalog or DataRuntime:
from muscles.data.ports import VectorSearchPort
vector = app.resource.connect("vector.docs", VectorSearchPort)
Resource config stays in the project:
data:
resources:
vector.docs:
type: qdrant
url_env: QDRANT_URL
api_key: !environ QDRANT_API_KEY
collection: docs
vector_size: 1536
distance: cosine
timeout: 3
prefer_grpc: false
The adapter creates the Qdrant client and collection lazily on vector search/write/delete,
explicit native access or data.doctor. Application code should use
VectorSearchPort; direct client access is only an advanced escape hatch with
native_client: true.
vector_size is required when a missing collection must be created. Request
dimensions are validated against the configured/existing collection, and
keyword payload indexes are created for standard AssetForge filter fields.
Embeddings are not generated by this adapter.
See muscular-example/example_data_qdrant_1 for an executable example.
Metadata
Release files for muscles-data-qdrant 0.2.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| muscles_data_qdrant-0.2.0.tar.gz | 17.3 kB | With provenance | Details for muscles_data_qdrant-0.2.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| muscles_data_qdrant-0.2.0-py3-none-any.whl | Python 3 | none | any | Details for muscles_data_qdrant-0.2.0-py3-none-any.whl |
Total release size: 27.5 kB
Release files / muscles_data_qdrant-0.2.0.tar.gz
| Download URL | muscles_data_qdrant-0.2.0.tar.gz |
|---|---|
| Size | 17.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
1228f1d6aae2a03770a2180188cdb0acc3dc1965f091dec78b5dad4526381da3
|
|
BLAKE2b-256 checksum How to use checksums |
d70489474f916bb5a09815c401ff3373e9a0005784f11e39cc760857b79cf7e0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 4, 2026.
Transparency logRelease files / muscles_data_qdrant-0.2.0-py3-none-any.whl
| Download URL | muscles_data_qdrant-0.2.0-py3-none-any.whl |
|---|---|
| Size | 10.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
55ba484b23cc0c4cd7657722a6054058814fca2188f8abd87bd6d6747aa51594
|
|
BLAKE2b-256 checksum How to use checksums |
79610eebf7a6540066ef1015231a5ef72e2a429b573997163af08250b7a95bce
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 4, 2026.
Transparency logSecurity for muscles-data-qdrant 0.2.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for muscles_data_qdrant-0.2.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 4, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.