Just for the archives - the removal of the "preservereOriginal" from the
"query" analizer solved my problem.
Thank you, Jack!
You need to have separate "index" and "query" analyzers for that field
type. The "query" analyzer would not have preserveOriginal="1", which
would generate an extra te
On 10/17/2012 7:24 AM, dirk wrote:
Hi,
I had a very similar Problem while searching in a bibliographic field called
"signatur". I could solve it by the help of additional Filterclasses. At the
moment I use the following Filters. Then it works for me:
...
-user@lucene.apache.org
Subject: Re: WordDelimiterFilter and the dot character
Hm, that makes sense, thank you, I will try this one.
Regards,
Istvan
You need to have separate "index" and "query" analyzers for that field
type. The "query" analyzer would not have pres
Hm, that makes sense, thank you, I will try this one.
Regards,
Istvan
You need to have separate "index" and "query" analyzers for that field
type. The "query" analyzer would not have preserveOriginal="1", which
would generate an extra term that would not match the exact term
sequence that wa
You need to have separate "index" and "query" analyzers for that field type.
The "query" analyzer would not have preserveOriginal="1", which would
generate an extra term that would not match the exact term sequence that was
indexed.
A query of "123 2012" would not split any terms and hence not
Hi,
I had a very similar Problem while searching in a bibliographic field called
"signatur". I could solve it by the help of additional Filterclasses. At the
moment I use the following Filters. Then it works for me:
...
