Skip to content
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

New event: update requested #351

Merged
merged 4 commits into from
Jan 29, 2024
Merged

Conversation

dandavison
Copy link
Contributor

@dandavison dandavison commented Jan 28, 2024

Add new event EVENT_TYPE_WORKFLOW_EXECUTION_UPDATE_REQUESTED for update reapply.

As explained in comments, this event will initially be restricted to updates reapplied during reset or replication. In the future we plan to use it for updates that are durable on admission.

dandavison added a commit to dandavison/temporalio-sdk-core that referenced this pull request Jan 28, 2024
rsync -auv ../api/temporal/ sdk-core-protos/protos/api_upstream/temporal/
@dandavison dandavison marked this pull request as ready for review January 29, 2024 03:33
@dandavison dandavison requested review from a team as code owners January 29, 2024 03:33
Copy link
Member

@cretz cretz left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This looks great to me and I hope in the near future, UpdateRequestedEventOrigin gets a UPDATE_REQUESTED_EVENT_ORIGIN_USER_REQUESTED or something to support admitted or general durability if the user wants it. To clarify, the SDKs should just ignore this event correct? If so, we'll want to remember server-side to set worker_may_ignore as true for this (though that's often more for backwards compat).

Comment on lines 58 to 60
// UpdateRequestedEventOrigin records why an
// WorkflowExecutionUpdateRequestedEvent was written to history. Note that not
// all update requests result in a WorkflowExecutionUpdateRequestedEvent.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
// UpdateRequestedEventOrigin records why an
// WorkflowExecutionUpdateRequestedEvent was written to history. Note that not
// all update requests result in a WorkflowExecutionUpdateRequestedEvent.
// Records why a
// WorkflowExecutionUpdateRequestedEvent was written to history. Note that not
// all update requests result in a WorkflowExecutionUpdateRequestedEvent.

You're free of Go! You don't have to start the comment with the message name!

Lol, doesn't really matter, that rule just always drives me nuts 😆 . The an->a change is a real typo though.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

:) fixed.

@dandavison dandavison merged commit 1dcc8e1 into temporalio:master Jan 29, 2024
4 checks passed
@dandavison dandavison deleted the update-reapply branch January 29, 2024 19:22
dandavison added a commit to dandavison/temporalio-sdk-core that referenced this pull request Feb 16, 2024
rsync -auv ../api/temporal/ sdk-core-protos/protos/api_upstream/temporal/
dandavison added a commit to dandavison/temporalio-sdk-core that referenced this pull request Feb 16, 2024
rsync -auv ../api/temporal/ sdk-core-protos/protos/api_upstream/temporal/
dandavison added a commit to temporalio/sdk-core that referenced this pull request Feb 16, 2024
* Update protos from temporalio/api#351

rsync -auv ../api/temporal/ sdk-core-protos/protos/api_upstream/temporal/

* Ignore UpdateRequested event
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants