Hi Michael, I suggest to wrap the query parser you're using now with a custom one. That's should help to handle the case where the query has a range with a large number.
I did something like that with Edismax. https://github.com/freedev/solr-synonyms-query-parser-plugin Take a look at the createParser parser method. When createParser is execute you can choose if you want rewrite the query parameters or use a custom list. Hope this helps, Vincenzo On Sun, Apr 10, 2016 at 11:38 PM, Michael Harkins <mp...@case.edu> wrote: > Well the originally architecture is out of my hands , but when someone > sends in a query like that, if the range is a large number , my system > basically shuts down and the cpu spikes with a large increase in > memory usage. The queries are for strings. The query itself was an > accident but I want to be able to prevent an accident from bringing > down the index. > > > > On Apr 10, 2016, at 12:34 PM, Erick Erickson <erickerick...@gmail.com> > wrote: > > > > OK, why is this a problem? This smells like an XY problem, > > you want to take some specific action, but it's not at all > > clear what the problem is. There might be other ways > > of doing this. > > > > If you're allowing regexes on numeric fields, using real > > number fields (trie) and using range queries is a much > > better way to go. > > > > Best, > > Erick > > > >> On Sun, Apr 10, 2016 at 9:28 AM, Michael Harkins <mp...@case.edu> > wrote: > >> Hey all, > >> > >> I am using lucene and solr version 4.2, and was wondering what would > >> be the best way to not allow regex queries with very large numbers. > >> Something like blah{1234567} or blah{1234, 123445678} > -- Vincenzo D'Amore email: v.dam...@gmail.com skype: free.dev mobile: +39 349 8513251
