Re: Search using MultiSearcher generates OOM on a 1GB total Partitioned indeces

2009-04-02 Thread Lebiram
, M From: Mark Miller To: java-user@lucene.apache.org Sent: Thursday, April 2, 2009 3:52:24 PM Subject: Re: Search using MultiSearcher generates OOM on a 1GB total Partitioned indeces You might try a constant score wildcard query (similar to a filter) - I think

Re: Search using MultiSearcher generates OOM on a 1GB total Partitioned indeces

2009-04-02 Thread Mark Miller
day, April 2, 2009 2:34:47 PM Subject: Re: Search using MultiSearcher generates OOM on a 1GB total Partitioned indeces Ah, I get it now. Given that you bumped your max clause up, it makes sense. I'm pretty sure that the wildcard expansion is the root or your memory problems. The folks on the

Re: Search using MultiSearcher generates OOM on a 1GB total Partitioned indeces

2009-04-02 Thread Erick Erickson
zzy search. > > Which goes back to the max clause problem. Lucene's default Max Clause is > 1024, is there any reason behind this max? > > Thanks, > > M > > > ________________ > From: Erick Erickson > To: java-user@lucene.apache.org > Sent: Thursday, April 2,

Re: Search using MultiSearcher generates OOM on a 1GB total Partitioned indeces

2009-04-02 Thread Lebiram
e.org Sent: Thursday, April 2, 2009 2:34:47 PM Subject: Re: Search using MultiSearcher generates OOM on a 1GB total Partitioned indeces Ah, I get it now. Given that you bumped your max clause up, it makes sense. I'm pretty sure that the wildcard expansion is the root or your memory problems. The fo

Re: Search using MultiSearcher generates OOM on a 1GB total Partitioned indeces

2009-04-02 Thread Erick Erickson
m guessing that might have caused the usage of too much memory? > > I'll try the explain on you've suggested. > > Thanks, > > M > > > > > ____________________ > From: Erick Erickson > To: java-user@lucene.apache.org > Sent: Wednesday, April 1, 2009 6:51:13 PM > Subjec

Re: Search using MultiSearcher generates OOM on a 1GB total Partitioned indeces

2009-04-02 Thread Lebiram
that might have caused the usage of too much memory? I'll try the explain on you've suggested. Thanks, M From: Erick Erickson To: java-user@lucene.apache.org Sent: Wednesday, April 1, 2009 6:51:13 PM Subject: Re: Search using MultiSearcher generate

Re: Search using MultiSearcher generates OOM on a 1GB total Partitioned indeces

2009-04-01 Thread Erick Erickson
Think about putting this query in Luke and doing an "explain" for details, but I'm surprised this is working at all without throwing TooManyClauses errors. Under the covers, Lucene expands your wildcards to all terms in the field that match. For instance, assume your document field has the fol

Search using MultiSearcher generates OOM on a 1GB total Partitioned indeces

2009-04-01 Thread Lebiram
Hi All, I have the following query on a 1GB index with about 12 million docs : As you can see the terms consist of wildcards... query.toString()=+(+content:g* +content:h* +content:d* +content:s* +content:a* +content:w* +content:b* +content:c* +content:m* +content:e*) +((+sender:cpuser9 +viewer