-
Notifications
You must be signed in to change notification settings - Fork 805
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add X-Cluster Child Workflow Completion Tasks #4336
Add X-Cluster Child Workflow Completion Tasks #4336
Conversation
5662806
to
654a8b2
Compare
cc5f267
to
4e4d8a9
Compare
8f4fd5b
to
9b8baf9
Compare
ac710b7
to
2267a72
Compare
// TODO: pass crossClusterTaskGenerators to processParentClosePolicy to add new cross | ||
// cluster tasks then move the call below after processParentClosePolicy call | ||
if len(crossClusterTaskGenerators) > 0 { | ||
t.generateCrossClusterTasks( |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
handle the returned error?
and the call should always be after processParentClosePolicy
I think, regardless of whether processParentClosePolicy
creates an x-cluster task or not?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Added the error handling.
I was planning move this down after the parent close policy changes. Could be better to keep the changes smaller and for one API. In the PR after this one it will be after the processParentClosePolicy
.
4baa4aa
to
ee48929
Compare
ee48929
to
8e7c80f
Compare
What changed?
Defining and persisting cross cluster tasks for RecordChildWorkflowExeuctionComplete task.
Why?
With this diff, child workflow notify the remote workflow about its completion.
How did you test it?
transfer_active_task_executor_test
Potential risks
Release notes
Documentation Changes