temporalio / temporalio/temporal
Add PARENT_CLOSE_POLICY_DISCONNECTED
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.
It is not possible to start child workflows in a fully disconnected mode which will not report completion/failure to the parent. It causes additional performance overhead as well as UnhandledCommand without any benefit:
Describe the solution you'd like
Add DISCONNECTED to the ParentClosePolicy. When a child is created with this policy, only its start (through ChildWorkflowExecutionStartedEvent) is reported to the parent. The child's completion and failure are not reported. The parent's completion doesn't affect the child as well.
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
Start by tracing the existing ParentClosePolicy handling and child workflow lifecycle tests. Use the issue's ChildWorkflowExecutionStartedEvent behavior as the acceptance criteria: a disconnected child reports only its start, is unaffected by parent completion, and does not report completion or failure to the parent.
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
- 45/100