From: Victor E. <vep...@is...> - 2012-02-16 13:21:04
|
Well, I first investigated this aspect a few days ago, when somebody posted a complaint about a maxClauseCount parameter in the Lucene index (forwarding post): On Tue, Feb 14, 2012 at 4:32 PM, <kie...@gm...> wrote: > Hello GeoNetwork users, > > we are searching for time ranges in about 54500 datasets inside the CSW and get the following error: > > Raised exception while searching metadata : org.apache.lucene.search.BooleanQuery$TooManyClauses: maxClauseCount is set to 16384 > > How to raise it? > > Kind regards, > Kieran After that, just googling for "maxClauseCount" brought up an interesting backstory to it. Apparently it is always hardcoded to some "high enough" value (which, according to who you ask, might be 16000, 32000 or 64000 records etc.), which is of course proverbially proven wrong, sooner or later. Fortunately, it can be changed through configuration. That's the only obvious hard & fast limit which is due only to an arbitrary constraint that I could identify. For the rest....I suppose interesting things could happen if someone exceeds a total of 2^31 records (might cause 32-bit integer overflows in certain software modules). |