[
https://issues.apache.org/jira/browse/JENA-1212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15387925#comment-15387925
]
ASF GitHub Bot commented on JENA-1212:
--------------------------------------
Github user afs commented on the issue:
https://github.com/apache/jena/pull/157
I thin it is better to consider them separately - first, get cancellable
sorts into the code base, then look at `Arrays.parallelSort`.
`Arrays.parallelSort` is going to need some care to make sure it does not
degrade concurrent requests and that is it properly behaves when cancelled.
What I'd like to know is how the current PR behaves in a live system. As it
builds on an existing facility, we can't take a "experimental feature" approach.
1. Does it completely address the motivating use case in production usage?
(May be it is only partial - we want to make one set of changes on master, not
a series changes.)
2. Does it lead to any advere/different effects? (including performance
comparisons though I doubt it will have an impact, because it replaces, it
would be good to know before it goes into becomes the master branch.)
I hope @ehedgehog can run tests in the with a modified Fuseki in a staging
setup for the system(s) that illustrated the problem in the first place.
> 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)
