>> Does the current Solr protocol 2.0 return a score?
Yes.
Solr returns a score, but only if you specify it in
the field list of a query (i.e.: &fl=*,score)... there
is a bit of a performance hit for returning it, so it
is not on by default.
However, remember that this score is composed of many
factors, including (if I recall correctly) frequencies
of matched terms in a record compared to the frequency
of these terms in the overall corpus. If you split
the corpus between different solr instances, your
scores may be skewed, if one half of your data set has
higher occurances of certain words or phrases than the
other half.
-Mark Backman
--- jason rutherglen <[EMAIL PROTECTED]> wrote:
> I think it would be best to write something from the
> ground up using the idea of multisearcher, which
> would use the XML HTTP client code to obtain results
> from each server. Seems like it would just do a
> merge. Does the current Solr protocol 2.0 return a
> score? I was thinking of adding this.
>
> - Original Message
> From: Chris Hostetter <[EMAIL PROTECTED]>
> To: solr-user@lucene.apache.org
> Sent: Wednesday, April 5, 2006 2:34:01 PM
> Subject: Re: Solr Multisearcher
>
>
> : > but the first step would probably be to provide
> the same
> : > level of functionality MultiSearcher
> :
> : Ahh, I was thinking the first step would be to try
> and use
> : MultiSearcher via RemoteSearcher/RemoteSearchable.
>
> Ah ... you were thinking something like this...
>
> MultiSearcher(Searchable[])
>--> SolrRemoteSearchable
> --HTTP-->
> http://solr:/select?qt=standard
>
> ...i was thinking of something like this...
>
> SolrMultiSearcher(URL[])
>--HTTP-->
>
http://solr:/select?qt=RemoteSerachableQueryHandler
>
> ...where MultiSearcher and SolrMultiSearcher inherit
> common logic from
> some subclass.
>
> My hunch is that the way MultiSearcher uses the
> Searchable API would make
> it impractical to use MultiSearcher as is, because
> it would probably
> making many "little" method calls that would each
> have to be sent as HTTP
> requests and involve XML parsing. I was assuming
> that it would be better
> to make a request handler that knew everything the
> multiseracher was going
> to be interested in and could return it all at once.
>
>
> But like i said, i don't really know anything about
> how MultiSearcher
> works, and i really don't understand
> RemoteSearchable ... so i could be
> way off.
>
>
> -Hoss
__
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
