New Golem specific host functions for implementing the Transaction API #11
Conversation
|
|
||
| /// Overrides the current retry policy associated with the worker. Following this call, `get-retry-policy` will return the | ||
| /// new retry policy. | ||
| set-retry-policy: func(new-retry-policy: retry-policy) -> (); |
There was a problem hiding this comment.
In theory this could be a resource, too, where committing would restore the retry policy to its value at the creation of the resource.
There was a problem hiding this comment.
Yes, I was thinking about it, but I think it is confusing if you create multiple ones simultaneously, as it is not guaranteed that you drop them in opposite order.
|
|
||
| /// Sets the worker's current persistence level. This can increase the performance of execution in cases where durable | ||
| /// execution is not required. | ||
| set-oplog-persistence-level: func(new-persistence-level: persistence-level) -> (); |
There was a problem hiding this comment.
In theory this could be a resource, too, where committing would restore the persistence level to its value at the creation of the resource.
There was a problem hiding this comment.
I was thinking not to for the same reason as for the retry policy
| /// True means side-effects are treated idempotent and Golem guarantees at-least-once semantics. | ||
| /// In case of false the executor provides at-most-once semantics, failing the worker in case it is | ||
| /// not known if the side effect was already executed. | ||
| set-idempotence-mode: func(idempotent: bool) -> (); |
There was a problem hiding this comment.
In theory this could be a resource, too, where committing would restore the idempotence level to its value at the creation of the resource.
Related to: