Hi Robert, On May 1, 2012, at 7:07pm, Robert Muir wrote:
> On Tue, May 1, 2012 at 6:48 PM, Ken Krugler <kkrugler_li...@transpac.com> > wrote: >> Hi list, >> >> Does anybody know if the Suggester component is designed to work with shards? > > I'm not really sure it is? They would probably have to override the > default merge implementation specified by SpellChecker. What confuses me is that Suggester says it's based on SpellChecker, which supposedly does work with shards. > But, all of the current suggesters pump out over 100,000 QPS on my > machine, so I'm wondering what the usefulness of this is? > > And if it was useful, merging results from different machines is > pretty inefficient, for suggest you would shard by term instead so > that you need only contact a single host? The issue is that I've got a configuration with 8 shards already that I'm trying to leverage for auto-complete. My quick & dirty work-around would be to add a custom response handler that wraps the suggester, and returns results with the fields that the SearchHandler needs to do the merge. -- Ken -------------------------- Ken Krugler http://www.scaleunlimited.com custom big data solutions & training Hadoop, Cascading, Mahout & Solr
