Enhance logic to populate BlobId data type correctly when simple blob is exactly max_chunk bytes
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.8k
- Forks
- 298
- Avg merge
- 21h 43m
- Merged PRs (30d)
- 9
Description
This is a follow-on to #940 where the BlobId flag was enhanced to include BlobDataType with three possible values:
- MetaData (composite blob)
- Simple (self-contained data blob)
- DataChunk (chunk that is part of a Composite blob)
The initial implementation, due to sequencing and asynchronicity, does not handle the case where a simple blob's size is exactly the configured chunking limit. This issue is filed to track the needed enhancement.
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 by reading issue #940 and the BlobId/BlobDataType implementation, then trace the asynchronous chunking path for a simple blob whose size equals the configured chunk limit. Reproduce that boundary case and verify that the resulting BlobId identifies the blob as Simple rather than as composite metadata or a data chunk.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend, distributed-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100