Allow passing messages longer then the Redis max bulk len
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 5
- Forks
- 6
- Avg merge
- 3h 52m
- Merged PRs (30d)
- 1
Description
LibMR should be able to pass message longer than Redis max bulk len. There should be other limit to the message len but the limit should be forced by LibMR with proper handling and error message (today Redis will just disconnect the connection and LibMR will have no good indication of what happened).
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 tracing LibMR's message-length handling and its Redis bulk-string interaction; the issue names no specific files or tests. Determine where oversized messages reach Redis and define the LibMR-side limit and error behavior. Done means oversized messages are handled by LibMR with a clear error instead of causing Redis to disconnect without useful feedback.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, redis
- Domain
- backend, databases
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100