On 17/05/2024 17:22, Holger Knublauch wrote:
Hi all,
am I missing something obvious or is it not yet possible to programmatically
abort SPARQL UPDATEs, like QueryExecutions can?
No, you aren't missing anything. Updates don't have a timeout.
Probably they could have nowadays.
There is a requirement on the dataset target of the update - it must
support a proper abort.
An Update can be several operations, separated by ";" and each
operation is completed before the next is attempted.
A timeout ought to abort the whole update otherwise, at best, the data
is partially updated, at worse (non-transactional usage), java data
structures may be corrupted.
Most datasets support a good enough abort but not a general dataset with
links to arbitrary graphs. A buffering dataset can be used for a good
enough abort.
Related, I also didn't see a way to set a timeout.
I guess for our use cases it would be sufficient if the abort would happen
during the WHERE clause iteration...
>
Thanks
Holger
Andy
