[
https://issues.apache.org/jira/browse/JENA-1212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15389423#comment-15389423
]
ASF GitHub Bot commented on JENA-1212:
--------------------------------------
Github user ajs6f commented on the issue:
https://github.com/apache/jena/pull/157
Yeah, I can see how some kind of "moving to phase X" signaling could be
real handy. I'm not familiar enough with the query machinery to understand
where that should live, though. I think that logging the cancellation is a very
good idea, perhaps at `INFO` level.
> allow ORDER BY sort to be cancelled
> -----------------------------------
>
> Key: JENA-1212
> URL: https://issues.apache.org/jira/browse/JENA-1212
> Project: Apache Jena
> Issue Type: Improvement
> Components: ARQ
> Reporter: christopher james dollin
> Priority: Minor
> Fix For: Jena 3.1.1
>
>
> When a query with an ORDER BY is cancelled, the component
> Arrays.sort() that sorts the chunk(s) of the result
> bindings runs to completion before the cancel finishes.
> [See QueryIterSort and SortedDataBag.]
> For a large result set, this results in a long wait
> before the cancelled request finally finishes. This
> can be inconvenient.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
