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 creat
There's some ability to time-limit queries so they
stop after a specified time. That does not do any
cost analysis ahead of time though.
Periodically there's some interest in a way to
short-circuit "expensive" queries through some
kind of query plan, but nothing committed yet.
Yeah, basically the
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
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
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}
