[
https://issues.apache.org/jira/browse/JENA-44?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stephen Allen updated JENA-44:
------------------------------
Attachment: JENA-44-ARQ_r1165687.patch
I made a few changes:
1) I'm now using -1 to shut off the spill to disk behavior
2) Changed to spillOnDiskSortingThreshold to be a Long instead of Integer
3) Removed the db.close() in the requestCancel()
4) Added a few more tests
For 3) the requestCancel() method is potentially called by another thread, and
thus cannot call the non-thread safe DataBag.close() method. Instead, we will
get proper cancellation from either the embedded iterator or the super class
(depending on which phase we are in, adding to or iterating over the databag).
> Support external sorting of bindings in ARQ
> -------------------------------------------
>
> Key: JENA-44
> URL: https://issues.apache.org/jira/browse/JENA-44
> Project: Jena
> Issue Type: New Feature
> Components: ARQ
> Reporter: Sam Tunnicliffe
> Assignee: Paolo Castagna
> Priority: Minor
> Attachments: JENA-44-0.patch, JENA-44-ARQ_r1165687.patch,
> JENA-44-Depends-on-JENA-99-r1157891.patch, JENA-44_ARQ_r1156212.patch,
> JENA-44_ARQ_r1165123.patch, JENA-44_ARQ_r8531.patch, JENA-44_ARQ_r8724.patch
>
>
> In QueryIterSort, the sorting of the contents of an Iterator<Binding> is done
> in memory, using Arrays.sort. This can be problematic where the set to be
> sorted is large. A possible solution could be to use an external, disk-backed
> algorithm. A hybrid approach may be better, whereby we attempt the in-memory
> sort, but when the number of bindings encountered goes over a certain number,
> resort to the disk-backed variant.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
