Hello Jack,
Thanks for your answer, it helped me gaining a deeper understandig what happens
at index time, and finding a solution myself:
It seems that putting the synonym filter in both filter chains (index and
query), setting expand="false", and putting the desired synonym first in the
row, does the trick:
Synonyms line (reversed order!):
orange, apfelsine
All documents containing "apfelsine" are now mapped to "orange", so there are
no more documets containing "apfelsine" that would match a wildcard-query for
"apfel*" ("Apfelsine" is a true synonym for "Orange" in german, meaning
"chinese apple". "Apfel" = apple, shouldnt match oranges).
Problem solved, thanks again for the help!
Johannes Rodenwald
----- Ursprüngliche Mail -----
Von: "Jack Krupansky" <j...@basetechnology.com>
An: solr-user@lucene.apache.org
Gesendet: Mittwoch, 13. Februar 2013 17:17:40
Betreff: Re: Index-time synonyms and trailing wildcard issue
By doing synonyms at index time, you cause "apfelsin" to be added to
documents that contain only "orang", so of course documents that previously
only contained "orang" will now match for "apfelsin" or any term query that
matches "apfelsin", such as a wildcard. At query time, Lucene cannot tell
whether your original document contained "apfelsin" or if "apfelsin" was
added when the document was indexed due to an index-time synonym.
Solution: Either disable index time synonyms, or have a parallel field (via
copyField) that does not have the index-time synonyms.
But... perhaps you should clarify what you really intend to happen with
these pseudo-synonyms.
-- Jack Krupansky
