Somehow a surround query is being constructed along the way. Search your logs
for “surround” and see if someone is maybe sneaking a q={!surround}… in there.
If you’re passing input directly through from your application to Solr’s q
parameter without any sanitizing or filtering, it’s possible a surround query
parser could be asked for.
—
Erik Hatcher, Senior Solutions Architect
http://www.lucidworks.com <http://www.lucidworks.com/>
> On Mar 24, 2015, at 8:55 AM, Ian Rose <ianr...@fullstory.com> wrote:
>
> Hi Erik -
>
> Sorry, I totally missed your reply. To the best of my knowledge, we are
> not using any surround queries (have to admit I had never heard of them
> until now). We use solr.SearchHandler for all of our queries.
>
> Does that answer the question?
>
> Cheers,
> Ian
>
>
> On Fri, Mar 13, 2015 at 10:08 AM, Erik Hatcher <erik.hatc...@gmail.com>
> wrote:
>
>> It results from a surround query with too many terms. Says the javadoc:
>>
>> * Exception thrown when {@link BasicQueryFactory} would exceed the limit
>> * of query clauses.
>>
>> I’m curious, are you issuing a large {!surround} query or is it expanding
>> to hit that limit?
>>
>>
>> —
>> Erik Hatcher, Senior Solutions Architect
>> http://www.lucidworks.com
>>
>>
>>
>>
>>> On Mar 13, 2015, at 9:44 AM, Ian Rose <ianr...@fullstory.com> wrote:
>>>
>>> I sometimes see the following in my logs:
>>>
>>> ERROR org.apache.solr.core.SolrCore –
>>> org.apache.lucene.queryparser.surround.query.TooManyBasicQueries:
>> Exceeded
>>> maximum of 1000 basic queries.
>>>
>>>
>>> What does this mean? Does this mean that we have issued a query with too
>>> many terms? Or that the number of concurrent queries running on the
>> server
>>> is too high?
>>>
>>> Also, is this a builtin limit or something set in a config file?
>>>
>>> Thanks!
>>> - Ian
>>
>>
