[JENA-2141] Query timeout may not be seen if during execution initialization.

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: Jena 4.1.0
• Fix Version/s: Jena 4.2.0
• Component/s: ARQ
• Assignee: Andy Seaborne
• Reporter: Andy Seaborne
• Created: 07/Aug/21 09:46
• Updated: 17/May/22 09:23
• Resolved: 21/Aug/21 12:47

Description

This follows on from JENA-2139. It is the more general case.

This is query 1 from the report from: Cristóbal Miranda on users@.

Query cancellation happens when an async timeout call queryIterator.abort in QueryExecutionBase.

But queryIterator is only set after the execution tree of iterators has been built, bottom-up.
If building takes a long time, the timeout callback can not call .abort.

The code needs to have a flag setup so it can be set at any time.

The mechanism added in Jena-2139, and similar code in QueryIterSort, QueryIterGroup and QueryIterTopN, which uses delayed initialization is better when this is possible. However, sometimes it is not easy to know when in the initialization phase.

One possibility is adding this to the ExecutionContext which exists and is passed to all query iterators during the setup phase.
 
QueryExecutionBase is being renamed as QueryExecDataset in PR#1003 as part of JENA-2128 in JENA-2125.

Issue Links

• is related to: JENA-2139 Query involving MINUS may not see query timeout.
• relates to: JENA-2328 Query timeouts failing when plan phase is long
• links to: GitHub Pull Request #1051