can not get "time" from api using the sdk
Open
Beginner friendly
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1.4k
- Forks
- 304
- Avg merge
- 2d 9h
- Merged PRs (30d)
- 37
Description
when delete by filter through api:
curl --location 'http://x:6333/collections/col/points/delete?wait=true' \
--header 'Content-Type: application/json' \
--header 'Authorization: ••••••' \
--data '{
"filter": {
"must": [
{
"key": "metadata.file_id",
"match": {
"value": "abcd6dee-03ca-4d38-a45f-51d941fe2c01"
}
}
]
}
}
'
result:
{
"result": {
"operation_id": 28272,
"status": "completed"
},
"status": "ok",
"time": 0.002382941
}
but through sdk, i can only get
class UpdateResult(BaseModel):
operation_id: Optional[int] = Field(default=None, description="Sequential number of the operation")
status: "UpdateStatus" = Field(..., description="")
So the "status" and "time" field is omitted, can I get then when using sdk?
usage:
import qdrant_client
async_qdrant_client = qdrant_client.AsyncQdrantClient()
res = await async_qdrant_client.delete(collection_name="col", points_selector=Filter(
must=[FieldCondition(key='metadata.file_id', match=MatchValue(value=file_id_str))]
))
res is: operation_id=30016 status=<UpdateStatus.COMPLETED: 'completed'>
no "status" and "time" field
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the delete entry point linked in async_qdrant_client.py around line 1129 and inspect the UpdateResult model shown in the issue. Compare the API response from the curl example with the SDK's returned model, then verify the delete call exposes the intended response fields consistently.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 70/100