Support migrate workflow from not using persistence caching to use caching
Open
3rd
important
in-review
- Dominant language
- Go
- Stars
- 661
- Forks
- 63
- PR merge metrics
- No merged PRs in 30d
Description
Currently the flag is set at workflow start, and store as a flag in persistence component.
Later when workflow definition enabling caching will not affect the existing workflow execution.
But ideally we should changing the definition should affect existing workflow execution as well
Contributor guide
Research direction
Start by tracing where the caching flag is set at workflow start and stored in the persistence component. Determine how workflow definition changes can affect existing executions, then verify that enabling caching after an execution starts produces the intended behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- distributed-systems
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100