Client does not check if it is able to connect to qdrant
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 415
- Forks
- 83
- Avg merge
- 2h 20m
- Merged PRs (30d)
- 3
Description
The qdrant client library currently does not verify if it is able to connect to qdrant server. If it is able to connect is only detectable after issuing the first api call.
For example:
QdrantConfig::from_url("http://localhost:6334")
.connect_timeout(Duration::from_secs(4))
.build()
.map_err(|e| Error::new(ErrorKind::Other, e))?;
succeeds immediately. Even if there is no server running at http://localhost:6334. This makes it difficult to observe connection errors. Tested on MacOS 26.1.
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 tracing QdrantConfig::from_url, connect_timeout, and build to see where connection setup currently stops, then compare that behavior with the first API call. Define the connection-error behavior for an unavailable server at http://localhost:6334 and verify it with a local connection test.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- api
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100