Thanks, again. :) Okay, so if one wants a distributed idf one should extend a searcher instead of the query-class.
But it doesn't seem to be pluggable, right? Well, for our purposes extending the query-class is enough, but just from beeing curious: Where should one starts if one wants to make some components pluggable? Since Real-Time-Search is an issue where I read about the idea of making things like the searcher pluggable, this could be beneficial to the community. Regards Yonik Seeley-2-2 wrote: > > On Wed, Feb 9, 2011 at 1:18 PM, Em <mailformailingli...@yahoo.de> wrote: >> How do they "store" these idfs for the current request so that the >> similarity is aware of them? > > The df (as opposed to idf) is requested from the searcher by the > weight, which then uses the similarity to produce the idf. See > TermWeight as an example. There's no out-of-the-box plugin to provide > alternate df values though, other than the Searcher interface. > > If you're doing custom enough scoring, then just implementing your own > query class is probably the way to go, but people might have other > ideas depending on the specifics of what you're trying to do. > > -Yonik > http://lucidimagination.com > > -- View this message in context: http://lucene.472066.n3.nabble.com/QueryWeight-for-Solr-tp2459933p2460718.html Sent from the Solr - User mailing list archive at Nabble.com.
