temporalio / temporalio/temporal
Continue-as-new with a different WorkflowID
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.
Workflows that call continue-as-new frequently can lead to hot shards.
Describe the solution you'd like
Many workflows rely on continue-as-new to process large datasets. Many of those workflows do not receive any external signals that require addressing them by WorkflowID.
The proposal is to support an option to continue-as-new to change WorkflowID. The whole chain of workflows still can be navigated through correspondent ids in the events as well listed using visibility queries.
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
No files, tests, or entry points are named. Start by examining the existing continue-as-new behavior and how WorkflowID, correspondent IDs, and visibility queries represent a workflow chain. Done means defining and validating an option that changes WorkflowID without breaking chain navigation or visibility.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100