qdrant / qdrant/vector-db-benchmark
Use `delete_client` wherever required
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 371
- Forks
- 155
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 4
Description
We recently introduced delete_client in the base client classes for adding pgvector in #91. We need to check if there are other places where this can help.
e.g. replace closable classes of OpenSearch and elastic with delete_client functionality (and check if it works fine)
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 by locating the base client classes where delete_client was introduced and search the client implementations for closable classes, especially OpenSearch and Elasticsearch. Compare those call sites with the existing delete_client behavior and verify that each applicable client still works correctly after the replacement.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- elasticsearch, python
- Domain
- databases
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100