Hi,
Am 20.08.2024 um 11:45 schrieb Greg Huber:
Thanks. Switching to SimpleQueryParser does resolve the exceptions,
before I was using classic.QueryParser/MultiFieldQueryParser. The
only difference is the tilde values. I guess these are now integers.
Basically, yes: The text is tokenized usi
Thanks. Switching to SimpleQueryParser does resolve the exceptions,
before I was using classic.QueryParser/MultiFieldQueryParser. The only
difference is the tilde values. I guess these are now integers.
On 19/08/2024 12:32, Uwe Schindler wrote:
Hi,
Basically, my only recommendation is to
Hi,
Basically, my only recommendation is to NOT use the standard query
parser in code that is useable from external users. Lucene has multiple
query parsers, the standard one is a strict one and has a stronmg syntax
and is therefor not targeted at end-users. This also applies to Solr:
Use dis
OK thanks, I do catch the exception and give a response.
I do a stopword check, but the fuzzy search syntax seems way more
complex as it does not like query statements SELECT AND etc.
if (!EnglishAnalyzer.ENGLISH_STOP_WORDS_SET.contains(term)
|| terms.length == 1)
On Sun, Aug 11, 2024 at 11:38 AM Greg Huber wrote:
> Is there a
> way to escape these or configure lecene just to return no results rather
> than an exception.
>
I don't think Lucene can handle it since the query parser and index
searcher are separate components, which are wired by some code.
I
Looking through my httpd logs I see lots of searches as such
/devbox/search?q=%29%20AND%203318%3D4385%20AND%20%287778%3D7778
ie : ) AND 3318=4385 AND (7778=7778
guess they might be fishing for something.
For the fuzzy search I use a different distance values and the default
is ~0.6
String
