qdrant / qdrant/vector-db-benchmark
Bug: Incomplete Dataset for yandex-1B-200-angular/yandex_t2i_gt_100k
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 371
- Forks
- 155
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 4
Description
What is the issue?
I am trying to run the benchmark on my own adding in a new vector database LanceDB specifically to compare filter search performance. When I try running the benchmark using this command:
poetry run python3 run.py --engines "lancedb-*"
I get the following error:
FileNotFoundError: [Errno 2] No such file or directory: '/Users/Yudhiesh/Projects/vector-db-benchmark/datasets/yandex-1B-200-angular/yandex_t2i_gt_100k/vectors.npy'
I noticed that the dataset that is downloaded is incomplete:
datasets/yandex-1B-200-angular
└── yandex_t2i_gt_100k
└── tests.jsonl
2 directories, 1 file
Based on the specification of the AnnCompoundReader since the files are .jsonl it is missing the actual vectors:
class AnnCompoundReader(JSONReader):
"""
A reader created specifically to read the format used in
https://github.com/qdrant/ann-filtering-benchmark-datasets, in which vectors
and their metadata are stored in separate files.
"""
VECTORS_FILE = "vectors.npy"
QUERIES_FILE = "tests.jsonl"
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 with run.py and the AnnCompoundReader definition, then inspect how yandex-1B-200-angular/yandex_t2i_gt_100k is downloaded or assembled. Reproduce the command with the lancedb-* engine pattern and verify that the dataset includes the vectors.npy file required by the reader and that the benchmark proceeds past dataset loading.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- databases
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100