[
https://issues.apache.org/jira/browse/LUCENE-2127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12796804#action_12796804
]
Grant Ingersoll commented on LUCENE-2127:
-----------------------------------------
I've started work on this by looking at a collector that does sorting after all
the results are collected. Now, I could simply sort on an array of ScoreDocs,
but I'd really like to be able to take advantage of the existing
Sort/SortField/FieldComparator stuff, but it seems really geared towards using
a PriorityQueue and managing an internal values array, whereas in my case I
already have the array allocated that I want to manage (well, for the most
part.)
The obvious choice is to punt and just provide score and doc id sorting, but
wanted to hear other people's thoughts
> Improved large result handling
> ------------------------------
>
> Key: LUCENE-2127
> URL: https://issues.apache.org/jira/browse/LUCENE-2127
> Project: Lucene - Java
> Issue Type: New Feature
> Reporter: Grant Ingersoll
> Assignee: Grant Ingersoll
> Priority: Minor
>
> Per
> http://search.lucidimagination.com/search/document/350c54fc90d257ed/lots_of_results#fbb84bd297d15dd5,
> it would be nice to offer some other Collectors that are better at handling
> really large number of results. This could be implemented in a variety of
> ways via Collectors. For instance, we could have a raw collector that does
> no sorting and just returns the ScoreDocs, or we could do as Mike suggests
> and have Collectors that have heuristics about memory tradeoffs and only
> heapify when appropriate.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
