Yes, the limit parameter is closest in concept to the LIMIT clause in SQL. It defaults to 100 so you'll see no more than that many facet values. There's also minCount which will establish a threshold if you don't want to see counts less than this number. It's common to set it to "1" so you don't see 0's.
~ David Smiley Author: http://www.packtpub.com/solr-1-4-enterprise-search-server/ On Mar 19, 2010, at 3:36 PM, Andy wrote: > Are you referring to the facet.limit parameter? > > If it is set to N, does that mean Solr only has to process N values, or that > Solr will still process all the values but only return the top N ones? > > > --- On Fri, 3/19/10, Smiley, David W. <dsmi...@mitre.org> wrote: > > From: Smiley, David W. <dsmi...@mitre.org> > Subject: Re: How many facet values are too many? > To: "solr-user@lucene.apache.org" <solr-user@lucene.apache.org> > Date: Friday, March 19, 2010, 9:07 AM > > On Mar 18, 2010, at 10:53 PM, Andy wrote: > >> My understanding is that too many facet values will decrease performance >> >> How many is too many? Are there any rules of thumb for this? >> >> 2 related questions: >> >> - I expect a facet field to have many values (values are user generated), >> any thing I can do to minimize the performance impact? >> >> - Any way to tell Solr to just at the top N values, kinda like the LIMIT >> clause in SQL? >> >> Thanks > > Not sure on the "how many is too many" question but I wouldn't be concerned; > Solr does faceting very well with highly optimized code. > The latter question -- absolutely. Standard stuff. Check out the wiki or buy > my book. > > ~ David Smiley > Author: http://www.packtpub.com/solr-1-4-enterprise-search-server/
