weaviate / weaviate/weaviate-python-client
Wait for async indexing function returning too early
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 227
- Forks
- 151
- Avg merge
- 3d 14h
- Merged PRs (30d)
- 11
Description
There seems to be a race condition in the wait_for_vector_indexing() function that the index status is reported for a moment as Ready while vectorQueueLength is 0 while objectCount is less than objectCountBefore + len(objectsInserted)
It would be convenient to check objectCount and the number of inserted objects in the batch to determine whether the indexing is done
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 locating wait_for_vector_indexing() in the Python client and inspect how it decides indexing is complete when vectorQueueLength reaches zero. Reproduce the reported race with a batch of inserted objects, then verify that completion waits until objectCount has increased by the batch size from its starting value.
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