qdrant / qdrant/vector-db-benchmark
Elastic vector limit should be 4096 instead of 2048
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 371
- Forks
- 155
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 4
Description
From v8.10 to v8.12 the dense vector limit move from 2048 to 4096. The benchmark should adjust it accordingly in https://github.com/qdrant/vector-db-benchmark/blob/5b9bffbe7fecff24b8885650049b9e1fdc798f00/engine/clients/elasticsearch/configure.py#L53
Further docs:
https://www.elastic.co/guide/en/elasticsearch/reference/current/dense-vector.html#index-vectors-knn-search
old v8.10 reference:
https://www.elastic.co/guide/en/elasticsearch/reference/8.10/dense-vector.html#dense-vector-params
new v8.12 reference:
https://www.elastic.co/guide/en/elasticsearch/reference/8.12/dense-vector.html#dense-vector-params
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
Open engine/clients/elasticsearch/configure.py at line 53 and compare the configured dense-vector limit with the linked Elasticsearch 8.12 documentation and the old 8.10 reference. Done means the benchmark uses the 4096 limit required for Elasticsearch 8.12.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- elasticsearch, python
- Domain
- databases
- Issue type
- Bug
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 55/100