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.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
