About bumping MaxBooleanQueries. You can certainly bump it up, but it's a legitimate question whether the user is well served by allowing that pattern as opposed to requiring 2 or 3 leading characters. The assumption behind the maxBooleanClause restriction is that when there get to be that many clauses, it's both costly in terms of processing and ultimately not much use to the search. YMMV of course, but a* will probably match lots of terms in every document.
Best Erick On Sun, Jan 1, 2012 at 4:12 PM, Michael Lissner <mliss...@michaeljaylissner.com> wrote: > On 01/01/2012 07:48 AM, Erick Erickson wrote: >> >> This may be the impetus for Hoss creating SOLR-2996. > > Yep, it is indeed, though I believe this problem can also happen when a user > searches for something like q=a* in a big index. I need a bigger index to > know for sure about that, but from what I've read so far, I'm fairly certain > that this problem is bigger than just the q=* search. > > I think my solution when this error is thrown is going to be to bump the > size of the maxBooleanClause and retry the query. Failing that, I'll have to > retry the query with highlighting off. > >> I suspect this will go away if you use the correct >> match-all-docs syntax, i.e. q=*:* rather than q=* > > It does, yes. > >> But I'm not sure what highlighting will do when there's >> nothing to highlight on (ie, no query terms to match >> against your text field). > > I believe it does nothing, thankfully. > > Mike
