Concurrent batches into an auto-schema-created collection lose objects
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 62/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- java
- Domain
- documentation
Research direction
Start with the client README and find the section covering imports or batching. Document the reported workaround: create the collection before importing, or send the first object separately before concurrent batches. The issue is done when the README explains the workaround and the race it addresses.
Written by the indexing model from the issue text.
Description
Problem
When several batches write concurrently into a collection that auto-schema has to create, they race to create it. The server rejects the losers' objects with:
auto-schema: create collection: class name ... already exists
In 4 of 5 runs, 2–4 of 40 objects were lost (Weaviate 1.39.7, server-side batching). Concurrent insertMany calls hit the same race, so this looks like a server-side issue rather than a client one.
Workaround
Create the collection before importing, or send the first object on its own before starting concurrent batches.
Suggestion
Document the workaround in the client README, and track the race in the core repo if it isn't tracked already.
- Dominant language
- Java
- Stars
- 34
- Forks
- 31
- Avg merge
- 2d 10h
- Merged PRs (30d)
- 2
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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.
More from weaviate/java-client
-
Filter.toString() throws IllegalFormatConversionException for withinGeoRange filtersPossibly taken @dudanogueira claimed this 7 days ago. Open
Difficulty 1/5 Under an hour Newbie friendliness 90/100
weaviate/java-client#638 ·
-
v6: VersionSupport rejects every 2.x server (major and minor are concatenated)Possibly taken @Ashlesha-17 claimed this 8 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
weaviate/java-client#631 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
weaviate/java-client#630 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
weaviate/java-client#629 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
weaviate/java-client#628 ·
All issues in weaviate/java-client
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 79/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 63/100
linagora/twake-calendar-side-service#1578 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
tchiotludo/akhq#3438 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
Paul-Austin-Oswego-CSC480-HCI521/gift-app#266 ·
Maintainers usually reply within 1 day