temporalio / temporalio/temporal
Add support for passing large arguments between activities
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 23.2k
- Forks
- 1.9k
- Avg merge
- 2d 8h
- Merged PRs (30d)
- 228
Description
Is your feature request related to a problem? Please describe.
From Slack:
I tried to pass a 30MB JSON from an activity as return to workflow and have workflow pass it to the next activity. It did not work. Save it as a blob somewhere and pass back the url would be the workaround I go for, but I do wonder if Temporal can have this built in. Let the activity call Temporal to save the blob in Cassandra/MySQL, returns the id of the blob to the workflow that can pass it on. Unify how large blob is passed from activity to activity, so user of Temporal do not have to think about it and do their own implementations
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
The issue names no files, tests, or entry points; begin by investigating how activity results are currently transferred and clarifying the intended blob-storage behavior for Cassandra and MySQL. Done would require a defined built-in mechanism for passing large activity results between activities, including its storage and retrieval contract.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cassandra, go, mysql
- Domain
- databases, distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100