-
Notifications
You must be signed in to change notification settings - Fork 758
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 sync workflow state task #2853
Conversation
SyncShardStatusTaskAttributes sync_shard_status_task_attributes = 5; | ||
SyncActivityTaskAttributes sync_activity_task_attributes = 6; | ||
// TODO: deprecate once kafka deprecation is done. | ||
HistoryMetadataTaskAttributes history_metadata_task_attributes = 7; | ||
HistoryTaskV2Attributes history_task_v2_attributes = 8; |
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.
is it possible to rename this field?
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.
Yes. We can do it. I will do it in a separate PR.
proto/internal/temporal/server/api/replication/v1/message.proto
Outdated
Show resolved
Hide resolved
workflowID := taskInfo.WorkflowID | ||
runID := taskInfo.RunID | ||
taskID := taskInfo.TaskID | ||
return p.processReplication( |
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.
not relevant to this PR, but I think we also need to handle namespace not found error inside processReplication()
. Probably also in replication executor on receiver end.
* Add sync workflow state task
What changed?
Add sync workflow state task
Why?
To replicate workflow state
How did you test it?
TODO: Integration test
Potential risks
Is hotfix candidate?