[
https://issues.apache.org/jira/browse/JENA-1212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15394261#comment-15394261
]
ASF GitHub Bot commented on JENA-1212:
--------------------------------------
Github user afs commented on the issue:
https://github.com/apache/jena/pull/157
It's sorting time inside of Fuseki that will really count. A few % is OK
for me - optimizing other things, e.g. the comparison process of
{{BindingComparator}} itself, is better to recover any loss.
I am a bit surprised the code makes any difference because the comparison
of two items is rather flexible ... which means not cheap.
I agree with @ajs6f - let's merge it and the see what's what such as
folding the cancellability into {{BindingComparator}} is one option.
> 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)
