-
Notifications
You must be signed in to change notification settings - Fork 246
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
EDU-3715: Python update-with-start docs #3250
Conversation
a3a1402
to
4432554
Compare
|
||
Use [`start_update_with_start_workflow`](https://python.temporal.io/temporalio.client.Client.html#start_update_with_start_workflow) to start an Update and wait for a [`WorkflowUpdateHandle`](https://python.temporal.io/temporalio.client.WorkflowUpdateHandle.html), and use `await update_handle.result()` to retrieve the result from the Update. | ||
|
||
Alternatively, use [`execute_update_with_start_workflow`](https://python.temporal.io/temporalio.client.Client.html#start_update_with_start_workflow) to start an Update and wait for the result in one go. |
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.
We should promote the execute...
approach a bit more. It is not simply an "alternative": it is generally preferable if they know that they will need the update result, as it may save one round trip.
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, you're right, we should emphasize the execute
version since we are emphasizing the use of UwS for low-latency updates. Switched.
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.
Left one minor comment, but I'm ok with what's there already.
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.
Changes look good. Holding on merge pending SDK publication.
|
||
In [Public Preview](/evaluate/development-production-features/release-stages#public-preview) in Temporal Cloud. | ||
|
||
Minimum Temporal Server version [Temporal Server version 1.26](https://github.com/temporalio/temporal/releases/tag/v1.26.0) |
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.
I had fixed this yesterday; the tag is wrong: d54486d
(same for the other link in TS)
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.
Oh, it seems I'm still using the wrong one in Java and Go.
Could you update that here while you're at it?
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.
Yep, done
DO NOT MERGE. Changes are approved, but on hold until SDK release. |
@brianmacdonald-temporal I've cherry-picked the non-blocked changes over here #3257 so it can be merged right now |
0045509
to
7d5ed69
Compare
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.
Changes look good.
TODO: