mirror of
https://github.com/hibiken/asynq.git
synced 2026-04-25 23:15:51 +03:00
[GH-ISSUE #501] [QUESTION] - Looking for some suggestions on data aggregation #1245
Labels
No labels
CLI
bug
designing
documentation
duplicate
enhancement
good first issue
good first issue
help wanted
idea
invalid
investigate
needs-more-info
performance
pr-welcome
pull-request
question
wontfix
work in progress
work in progress
work-around-available
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/asynq#1245
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @sujit-baniya on GitHub (Jun 22, 2022).
Original GitHub issue: https://github.com/hibiken/asynq/issues/501
Discussed in https://github.com/hibiken/asynq/discussions/500
Originally posted by sujit-baniya June 22, 2022
Hello,
I've been trying to implement Workflow using this library.
https://github.com/sujit-baniya/asynq/blob/master/flow.go
For the purpose, I've implemented flow and this example works for simple Edge and Node implementation
https://github.com/sujit-baniya/asynq/blob/master/examples/asynq_worker.go
The example works for
I'm trying find solution where a edge/loop has multiple output. Since there would be multiple output, at some point it is required to combine such data.
For e.g.
NodeA with key A
NodeB with key B (generates phone_valid field)
NodeC with key C (generates email_valid field)
NodeD with key D
Edge is created from A -> B
Edge is created from A -> C
Edge is created from B -> D
Edge is created from C -> D
I'm trying to get aggregated data received from above flow.
If I pass data like
{"phone": "123456789", "email": "abc@example"}to Node A, I would be expecting{"phone": "123456789", "email": "abc@example", "phone_valid": true, "email_valid": true}on Node DPlease suggest some ideas.
@hibiken commented on GitHub (Jun 26, 2022):
Duplicate of #500