On Sun, Feb 19, 2012 at 10:23 AM, Benson Margulies
wrote:
> thanks, that's what I needed.
>
Thanks for bringing this up, I think its a common issue, I created
https://issues.apache.org/jira/browse/LUCENE-3799 to hopefully improve
the docs situation.
--
lucidimagination.com
thanks, that's what I needed.
On Feb 19, 2012, at 9:51 AM, Robert Muir wrote:
> On Sun, Feb 19, 2012 at 9:21 AM, Benson Margulies
> wrote:
>> If I have a lot of segments, and an executor service in my searcher,
>> the following runs out of memory instantly, building giant heaps. Is
>> there an
By passing Integer.MAX_VALUE you are requesting Lucene to allocate a priority
queue for collecting results with that size, this OOMs. With Lucene if you are
using TopDocs, the idea is to only get a limited amount of Top-Ranking
documents to display search results. The user is not interested in t
On Sun, Feb 19, 2012 at 9:21 AM, Benson Margulies wrote:
> If I have a lot of segments, and an executor service in my searcher,
> the following runs out of memory instantly, building giant heaps. Is
> there another way to express this? Should I file a JIRA that the
> parallel code should have some
