[
https://issues.apache.org/jira/browse/JENA-48?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12995247#comment-12995247
]
Andy Seaborne commented on JENA-48:
-----------------------------------
Not only subqueries (which are in SPARQL 1.1 and ARQ). A query with "group by"
and "order by" has nesting of the query processing stages that need cancelling
in the middle of processing steps that can take a long time with nothing coming
out until the processing is complete. The subqueries effect means there isn't
a fixed structure to the execution plan.
> Check use of exception in QueryIterGroup / QueryIterSort .cancel()
> ------------------------------------------------------------------
>
> Key: JENA-48
> URL: https://issues.apache.org/jira/browse/JENA-48
> Project: Jena
> Issue Type: Sub-task
> Components: ARQ
> Reporter: Andy Seaborne
> Priority: Minor
>
> QueryIterAbortCancellationRequestException
> Can we use cancelRequest and not risk bypassing iteraors in complex satcks of
> iteraors (e.g. subqueries)?
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
