: 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
iorixxx wrote:
>
> CustomSimilarityFactory that extends
> org.apache.solr.schema.SimilarityFactory should do it. There is an example
> CustomSimilarityFactory.java under src/test/org...
>
This is exactly what I was looking for... this is very similar ( no put
intended ;) ) to the updateProcess
> 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...
iorixxx wrote:
>
> it is in schema.xml:
>
>
>
How would you configure the tfBaselineTfFactors and LengthNormFactors when
configuring via schema.xml? Do I have to create a subclass that hardcodes
these values?
--
View this message in context:
http://lucene.472066.n3.nabble.com/SweetSpotSimi
> 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.
iorixxx wrote:
>
> it is in schema.xml:
>
>
>
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?
--
View this message in context:
http://lucene.472066.n3.nabble.com/Sweet
> 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
