openresty / openresty/lua-resty-redis
[Feature Request] Pipeline coroutine safety
Open
Nobody has claimed this yet.
- Dominant language
- Lua
- Stars
- 2k
- Forks
- 447
- Avg merge
- 2h 24m
- Merged PRs (30d)
- 3
Description
When using a pipeline combined with a coroutine, some commands might get mixed into the pipeline. Please consider introducing pipeline objects, e.g.:
local pipe = red:start_pipeline()
pipe:set(...)
-- ...
for result in ipairs(pipe:commit()) do
-- ...
end
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
The issue names no files or tests; start by locating the existing pipeline and coroutine command-handling code in the repository. Compare that behavior with the proposed start_pipeline, command, and commit flow, and define done as preventing commands from different coroutine pipelines from mixing while preserving pipeline results.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- lua, redis
- Domain
- databases
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100