[bug] upsert_points_blocking() api blocks indefinitely without any clear debug message
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 415
- Forks
- 83
- Avg merge
- 2h 20m
- Merged PRs (30d)
- 3
Description
Hey folks,
I'm creating a custom payload and committing data to Qdrant. The upsert operation works perfectly for about a thousand points, then gets blocked indefinitely. There was no debug information available to identify what could have gone wrong.
client
.upsert_points_blocking(COLLECTION_NAME, new, None)
.await
.map_err(|_| Box::new(CommitError::QdrantError))?;
Contributor guide
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 by reproducing the custom-payload upsert through upsert_points_blocking(), using a workload of about 1,000 points and observing where it blocks. Investigate the available error or debug output around that call; done means the indefinite block is addressed and the failure provides clear diagnostic information.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100