slotBuffer is all ZEROs for a specific key
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 939
- Forks
- 180
- PR merge metrics
- No merged PRs in 30d
Description
We recently ran into strange issue where a **_StoreReader.get(Object key)_** given the key returned a null, but when we do **_StoreReader.iterable()_** we could see the key and the value printer correctly.
This happened only for one particular key. Debugging in the paldb library and see that the **_slotBuffer_** is loaded with ZERO’s for that particular key and **_offset_** results in a ZERO.
I have attached screenshot of the debug point. I am unable to re-produce this with the same key and dataset.
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 at StoreReader.get(Object key) and compare its behavior with StoreReader.iterable() for the reported key. Trace the reported slotBuffer and offset values, but first establish a reproducible case because the same key and dataset no longer reproduce the issue. Done means get returns the key and value that iterable exposes, with the cause identified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- database
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100