sie-qdrant
SIE integration for Qdrant.
Installation
pip install sie-qdrant
Dense embeddings
from qdrant_client import QdrantClient
from qdrant_client.models import Distance, VectorParams, PointStruct
from sie_qdrant import SIEVectorizer
vectorizer = SIEVectorizer(base_url="http://localhost:8080", model="BAAI/bge-m3")
qdrant = QdrantClient("http://localhost:6333")
qdrant.create_collection(
collection_name="documents",
vectors_config=VectorParams(size=1024, distance=Distance.COSINE),
)
texts = ["first doc", "second doc"]
vectors = vectorizer.embed_documents(texts)
qdrant.upsert(
collection_name="documents",
points=[
PointStruct(id=i, vector=v, payload={"text": t})
for i, (t, v) in enumerate(zip(texts, vectors))
],
)
query_vec = vectorizer.embed_query("search text")
results = qdrant.query_points(
collection_name="documents", query=query_vec, limit=5
)
Named vectors (dense + sparse)
SIE's multi-output encode produces dense and sparse vectors in one call.
Qdrant supports sparse vectors natively via SparseVector(indices, values),
so no expansion to full vocabulary length is needed:
from qdrant_client import QdrantClient
from qdrant_client.models import (
Distance, VectorParams, PointStruct,
SparseVectorParams, SparseVector,
)
from sie_qdrant import SIENamedVectorizer
vectorizer = SIENamedVectorizer(
base_url="http://localhost:8080",
model="BAAI/bge-m3",
output_types=["dense", "sparse"],
)
qdrant = QdrantClient("http://localhost:6333")
qdrant.create_collection(
collection_name="documents",
vectors_config={"dense": VectorParams(size=1024, distance=Distance.COSINE)},
sparse_vectors_config={"sparse": SparseVectorParams()},
)
named = vectorizer.embed_documents(["hello world"])
qdrant.upsert(
collection_name="documents",
points=[
PointStruct(
id=0,
vector={
"dense": named[0]["dense"],
"sparse": SparseVector(**named[0]["sparse"]),
},
payload={"text": "hello world"},
)
],
)
Storage advantage: Unlike integrations that expand sparse vectors to full vocabulary length (~30K floats), Qdrant stores sparse vectors in their native indices+values form, making hybrid search storage-efficient.
Testing
# Unit tests (no server needed)
pytest
# Integration tests (requires SIE + Qdrant)
pytest -m integration
1 maintainer
Metadata
1 maintainer
Release files for sie-qdrant 0.10.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 | |
|---|---|---|---|
| sie_qdrant-0.10.0.tar.gz | 10.2 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| sie_qdrant-0.10.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 15.2 kB
Release files / sie_qdrant-0.10.0.tar.gz
| Download URL | sie_qdrant-0.10.0.tar.gz |
|---|---|
| Size | 10.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b41cd036f1d4234d8c353647bd109e169ed59c7de6de63c76047a35f4e15afea
|
|
BLAKE2b-256 checksum How to use checksums |
892838eedc2e3a50bde71fcfe6130f1e018bf79b34514a26252960aa5de45f7d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Oct 9, 2026.
Transparency logRelease files / sie_qdrant-0.10.0-py3-none-any.whl
| Download URL | sie_qdrant-0.10.0-py3-none-any.whl |
|---|---|
| Size | 5.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
0e6c74396c183056a04613bb4af903889c74400fa467530d80a2f1fbff8a1303
|
|
BLAKE2b-256 checksum How to use checksums |
41f79f121f40dae0b20bf211e7c9d0e23c1014bf1da6ed8ec51d36530011543d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Oct 9, 2026.
Transparency log
