Re: [CAUTION] Re: Use of ShingleFilter causing very large BooleanQuery structures in Solr 7.1

2019-03-22 Thread Hubert-Price, Neil
One other question Is there a system level configuration that can change the default for the sow= parameter? Can it be flipped to have the default set to true? Many Thanks, Neil On 22/03/2019, 08:36, "Hubert-Price, Neil" wrote: Thanks Erick, that makes sense.

Re: Use of ShingleFilter causing very large BooleanQuery structures in Solr 7.1

2019-03-22 Thread Hubert-Price, Neil
a single token: > > +productdetails_tokens_en:9612194002_9612194002_9612194002) > > Best, > Erick > >> On Mar 21, 2019, at 3:10 PM, Hubert-Price, Neil >> wrote: >> >> Surely the tokenizer splits on white space anyway, or it wouldn't work? >

Re: Use of ShingleFilter causing very large BooleanQuery structures in Solr 7.1

2019-03-21 Thread Hubert-Price, Neil
ere Erick > On Mar 21, 2019, at 1:11 AM, Hubert-Price, Neil wrote: > > Hello Erick, > > This is the first time I've had reason to use the mailing list, so I wasn't aware of the behaviour around attachments. See below, links to the images tha

Re: Use of ShingleFilter causing very large BooleanQuery structures in Solr 7.1

2019-03-21 Thread Hubert-Price, Neil
=true". Here’s some background: https://lucidworks.com/2017/04/18/multi-word-synonyms-solr-adds-query-time-support/ I have no actual, you know, _knowledge_ that it’s related but it’d be super-easy to try and might give a clue. Best, Erick > On Mar 20

Use of ShingleFilter causing very large BooleanQuery structures in Solr 7.1

2019-03-20 Thread Hubert-Price, Neil
Hello All, We have a recently upgraded system that went from Solr 4.6 to Solr 7.1 (used as part of an ecommerce application). In the upgraded version we are seeing frequent issues with very high Solr memory usage for certain types of query, but the older 4.6 version does not produce the same r