How to Fetch Async Operation Status in Qdrant #6938
Replies: 2 comments
-
|
qdrant does not expose tracking for individual operations, as it creates too much overhead. But you have the following options:
Usually, the latency of individual operation is quite small, unless you are sending huge batches or running a lot of concurrent updates |
Beta Was this translation helpful? Give feedback.
-
|
Great question — we’ve hit this wall too when designing async-aware RAG pipelines that rely on vector update confirmations. One trick we use: when wait=True isn't granular enough (especially in chained RAG updates across memory buffers), we apply a semantic acknowledgment pattern — basically a dummy vector insert as a commit marker, then query for that as a logical checkpoint. Also, if you're curious how memory handoff across async LLM calls tends to break reasoning, we documented that in WFGY ProblemMap #7 – “Memory Breaks Across Sessions” – including a stable fix if you’re running into async-memory desync during RAG cycles. Let me know if helpful — always happy to share implementation examples. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
I am performing an asynchronous upsert operation on a Qdrant collection using Python's asyncio along with the qdrant-client library. Upon submission, I receive a response containing an operation_id and a status marked as Acknowledged.
I would like to know if there is an API endpoint or a method in the qdrant-client Python library that allows me to check the status of this asynchronous operation using the operation_id. Specifically, I want to determine whether the task has completed or is still in progress.
Any guidance, references, or documentation links related to this would be greatly appreciated.
Beta Was this translation helpful? Give feedback.
All reactions