Uh oh!
There was an error while loading. Please reload this page.
Optimize Continue As New And Solve Missed Raised Events - #251
Conversation
adarsh1
commented
Jan 19, 2019
Chris Gillum (cgillum)
commented
Jan 19, 2019
Note: this fixes Azure/azure-functions-durable-extension#67 |
Chris Gillum (cgillum)
left a comment
There was a problem hiding this comment.
I'm super-excited to have this change! Relatively minor CR feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
adarsh1
commented
Jan 22, 2019
Need to add one more change for the azurestorageprovider which is to also commit the old runtime state if it is instance store backed |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
| namespace DurableTask.Core.Command | ||
| { | ||
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
| continuedAsNewMessage = null; | ||
| TraceHelper.TraceInstance( | ||
| TraceEventType.Verbose, |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
This PR aims to optimize ContinueAsNew so that an orchestration continues in memory in the dispatcher if it can instead of enqueueing a new task message.
With this Events Raised After a continueAsNew has been executed will also be collected and carried over to the next iteration of the orchestration. This a feature that can be opted out of by specifying SkipEventsOnContinuation as true in the OrchestrationService.