You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When something fails - eg an internet outage, it's super annoying to have to restart the entire set of requests. It would be useful instead if there was some form of checkpointing.
Thinking of
runHttp {
call('...') {
data = Checkpoint(FileDataSupplier(...))
}
}
The checkpoint will work via using a file based at a {cwd}/.fetchDSL folder. Each invocation can be named, or otherwise a 'global' checkpoint will be used in which case it's unsafe to run multiple checkpoints at the same time.
The easiest way to do checkpointing will be adding metadata to a envelope that encapsulates the request. This context object will be able to be received later to identify when a request has made it through the pipeline and can be marked as successful.
Another requirement is deterministic ordering of the input if checkpointing needs index based skips. Given that the concurrent nature of the produceHttp section is largely to handle the case of slow before sections, this should be fine. Though it would potentially lose the ability to use a slow (but thread safe) data provider.
The text was updated successfully, but these errors were encountered:
When something fails - eg an internet outage, it's super annoying to have to restart the entire set of requests. It would be useful instead if there was some form of checkpointing.
Thinking of
The checkpoint will work via using a file based at a
{cwd}/.fetchDSL
folder. Each invocation can be named, or otherwise a 'global' checkpoint will be used in which case it's unsafe to run multiple checkpoints at the same time.The easiest way to do checkpointing will be adding metadata to a envelope that encapsulates the request. This context object will be able to be received later to identify when a request has made it through the pipeline and can be marked as successful.
Another requirement is deterministic ordering of the input if checkpointing needs index based skips. Given that the concurrent nature of the
produceHttp
section is largely to handle the case of slowbefore
sections, this should be fine. Though it would potentially lose the ability to use a slow (but thread safe) data provider.The text was updated successfully, but these errors were encountered: