[FEATURE REQUEST] Jobs aggregation
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 5.7k
- Forks
- 179
- Avg merge
- 15h 43m
- Merged PRs (30d)
- 13
Description
I wonder if this feature is on your roadmap.
TL;DR;
Job aggregation allows you to enqueue multiple jobs successively, and have them passed to the Worker together rather than individually. The feature allows you to batch multiple successive operations into one.
You can see the usecase and the original PR:
https://github.com/hibiken/asynq/issues/339
Final docs
https://github.com/hibiken/asynq/wiki/Task-aggregation
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 the linked Asynq issue 339, original pull request, and the final task-aggregation documentation to understand the proposed behavior and tradeoffs. Then identify the River worker and job-queue entry points involved; done should mean successive jobs can be grouped and delivered to a worker together with documented, tested behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend, distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100