I'm working with Lucene 4.0 and I didn't use lucene's QueryParser, so
setAllowLeadingWildcard() is irrelevant.
I also realised the issue wasn't with querying, but it was indexing whihch
left the terms with leading special character out.
My goal was to do a fuzzymatch by creating a trigram index. T
thanks Erik.
I tried putting the query in "double quotes" and it made some difference
but still not exactly what I'm looking for.
so what's my best solution? to avoid using the QueryParser and instead
"parse" the query myself? is there a different (better) query parser
for this situation?
The analyzer through QueryParser is invoked for each "clause" and thus in your
example it's invoked 4 times and thus each invocation only sees one word/term.
Erik
On Jan 13, 2013, at 2:13, "Igal @ getRailo.org" wrote:
> hi,
>
> I've created an Analyzer that performs a few filtering tasks
