I was curious as to how the caching would be handled. In a world where there is a massive realtime virtual index, should the sorting and caching be handled on dedicated servers separate from the index machines?
----- Original Message ---- From: Chris Hostetter <[EMAIL PROTECTED]> To: solr-user@lucene.apache.org Sent: Wednesday, April 5, 2006 2:10:41 PM Subject: Re: Solr Multisearcher : Lucene's MultiSearcher can already get you the top "n" documents, : filtered, and sorted by score or other criteria. right, that logic could probably be refactored into a base class so both MultiSearcher(Searchable[]) and some new SolrMultiSearcher(URL[]) could use them ... my question is more what all in the Searchale interface does MultiSearcher currently use when it queries/merges the multiple sub-searchers, and how can we mimic that api (efficiently) in a RequestHandler. : We could create a SolrMultiSearcher that builds on that. One gets : into issues of how to do high availability and redundancy though : (which MultiSearcher doesn't currently handle AFAIK) true that ... but the first step would probably be to provide the same level of functionality MultiSearcher -- any cool redundency handling built after that could probably be refactored and shared. -Hoss
