Lazy load base64Binary and hexBinary
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 246
- Forks
- 85
- Avg merge
- 6d 1h
- Merged PRs (30d)
- 22
Description
A string is required to create one of the binary types. Would it be possible to have a constructor accepting bytes that doesn't set the stringValue before serializing it? This would allow RumbleDB to efficiently deal with intermediate binaries where serializing them isn't necessary (imagine a query that downloads an image and returns what objects are in it as text)
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 locating the base64Binary and hexBinary implementations and tracing how their string values are created before serialization. Determine how a byte-accepting constructor could defer that work while preserving the existing serialized output, then add or update tests covering construction and serialization.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100