Aklakan commented on PR #2822: URL: https://github.com/apache/jena/pull/2822#issuecomment-2464749534
> If a global timeout for queries is set, then that will be picked up by the update execution where it wasn't 5.2 and earlier. * One option would be to introduce `ARQ.updateTimeout` and have the UpdateEngineWorker (or perhaps already at `builder.build()`) do ```java cxt.set(ARQ.queryTimeout, cxt.get(ARQ.updateTimeout)) ``` * Furthermore, there could be an additional `ARQ.requestType` context symbol for query and update requests (and perhaps dataset ones; c.f. `LinkDataset`). And the appropriate timeout value is picked based on the context's request type which might be cleaner than having to mutate the context. I'd say that the basic updateTimeout setting should affect the overall timeout of an update request - not per sub-update. The suggestions should be backward compatible with the existing behavior (but may require a change for computing the effective timeout in the query exec). -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
