: Side question. How would I know if a configuration option can also take a
: factory class.. like in this instance?
by reading the example schema.xml...
-Hoss
ded ;) ) to the updateProcessorFactory configuration in
solr-config.xml. The wiki should probably include this information.
Side question. How would I know if a configuration option can also take a
factory class.. like in this instance?
--
View this message in context:
http://lucene.472066.n3.nabble.com/Swee
> How would you configure the tfBaselineTfFactors and
> LengthNormFactors when
> configuring via schema.xml?
CustomSimilarityFactory that extends org.apache.solr.schema.SimilarityFactory
should do it. There is an example CustomSimilarityFactory.java under
src/test/org...
6.n3.nabble.com/SweetSpotSimilarity-tp922546p928730.html
Sent from the Solr - User mailing list archive at Nabble.com.
> Thanks. Im guessing this is all or nothing.. ie you can't
> you one similarity
> class for one request handler and another for a separate
> request handler. Is
> that correct?
correct, also re-index is required. length norms are calculated and stored at
index time.
472066.n3.nabble.com/SweetSpotSimilarity-tp922546p922622.html
Sent from the Solr - User mailing list archive at Nabble.com.
> Would someone mind explaining how this differs from the
> DefaultSimilarity?
The difference is length normalization. Default one punishes long documents.
"Sweet one computes to a constant norm for all lengths in
the [min,max] range (the "sweet spot"), and smaller norm
values for lengths out of
e.com/SweetSpotSimilarity-tp922546p922546.html
Sent from the Solr - User mailing list archive at Nabble.com.
