Don't highlight on it. As Chris pointed out, it's the_highlighting_
that builds this ginormous clause. Just something like _searching_
on text:* has short-circuits in the code that refrain from this
expansion.
Best
Erick
On Mon, Mar 19, 2012 at 8:42 AM, Darren Govoni wrote:
> true. but how can
true. but how can you find documents containing that field without expanding
1000 clauses?
--- Original Message ---
On 3/19/2012 07:24 AM Erick Erickson wrote:bq: So all I want to do is a simple
"all docs with something in this field,
and to highlight the field"
But that doesn't reall
bq: So all I want to do is a simple "all docs with something in this field,
and to highlight the field"
But that doesn't really make sense to do at the Solr/Lucene level. All
you're saying is that you want that field highlighted. Wouldn't it be much
easier to just do this at the app level whenever
Thanks for the tip Hoss.
I notice that it appears sometimes and was varying because my index runs
would sometimes have different amount of docs, etc.
So all I want to do is a simple "all docs with something in this field,
and to highlight the field".
Is the query expansion to "all possible term
: 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 into a giant boolea
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.
>
> Any ideas? This is
