Any changes you make related to stemming or normalization are likely
going to require a re-index, just how it goes, just how solr/lucene
works. What you can do just by normalizing at query time is limited,
almost any good solution to this type of problem is going to require
normalization at index time.
If you're going to be fiddling with a production solr, it pays to figure
out a workflow such that you can introduce indexing changes without
downtime, this is not the last time you'll have to do it.
On 8/1/2011 12:35 PM, thomas wrote:
Thanks Alexei,
Thanks Paul,
I played with the solr.PhoneticFilterFactory. Analysing my query in solr
admin backend showed me how and that it is working. My major problem is,
that this filter needs to be applied to the index chain as well as to the
query chain to generate matches for our search. We have a huge index at this
point and i'am not really happy to reindex all content.
Is there maybe a more subtle solution which is working by just manipulating
the query chain only?
Otherwise i need to backup the whole index and try to reindex overnight when
cms users are sleeping.
I will have a look into the ColognePhonetic encoder. Im just afraid ill have
to reindex the whole content there as well.
Thomas
--
View this message in context:
http://lucene.472066.n3.nabble.com/German-language-specific-problem-automatic-Spelling-correction-automatic-Synonyms-tp3216278p3216414.html
Sent from the Solr - User mailing list archive at Nabble.com.
