ms. Why
> should
> > they all become explicit query elements? Seems overkill and
> > underperformant.
> >
> > Is there a another way with Lucene or not really?
> >
> > On Thu, 2012-03-08 at 16:18 -0800, Chris Hostetter wrote:
> >> : I am suddenly ge
Lucene or not really?
>
> On Thu, 2012-03-08 at 16:18 -0800, Chris Hostetter wrote:
>> : I am suddenly getting a maxClauseCount exception for no reason. I am
>> : using Solr 3.5. I have only 206 documents in my index.
>>
>> Unless things have changed the reason you
> they all become explicit query elements? Seems overkill and
> underperformant.
>
> Is there a another way with Lucene or not really?
>
> On Thu, 2012-03-08 at 16:18 -0800, Chris Hostetter wrote:
>> : I am suddenly getting a maxClauseCount exception for no reason. I am
stetter wrote:
> : I am suddenly getting a maxClauseCount exception for no reason. I am
> : using Solr 3.5. I have only 206 documents in my index.
>
> Unless things have changed the reason you are seeing this is because
> _highlighting_ a query (clause) like "type_s:[*+TO+*]&q
: I am suddenly getting a maxClauseCount exception for no reason. I am
: using Solr 3.5. I have only 206 documents in my index.
Unless things have changed the reason you are seeing this is because
_highlighting_ a query (clause) like "type_s:[*+TO+*]" requires rewriting
it in
Set maxBooleanClauses in your solrconfig.xml higher, default is 1024.
Your query blast this limit.
Regards
Vadim
2012/2/22 Darren Govoni
> Hi,
> I am suddenly getting a maxClauseCount exception for no reason. I am
> using Solr 3.5. I have only 206 documents in my index.
>
>
Hi,
I am suddenly getting a maxClauseCount exception for no reason. I am
using Solr 3.5. I have only 206 documents in my index.
Any ideas? This is wierd.
QUERY PARAMS: [hl, hl.snippets, hl.simple.pre, hl.simple.post, fl,
hl.mergeContiguous, hl.usePhraseHighlighter, hl.requireFieldMatch
