It seemed handy in the mentioned case where its not certain if there are products in each of the budgetcategories so you simply ask them all, and only get back the categories which contain at least 1 product.
>From a functional perspective to me that's kind of on par with doing facet.mincount=1 (the only difference being that the data just doesn't happen to be in 1 field). However, the client ideally shouldn't need to bother with that difference imho. Cheers, Geert-Jan Erik Hatcher wrote: > > > On Dec 5, 2007, at 8:33 AM, Yonik Seeley wrote: >> On Dec 5, 2007 7:45 AM, Erik Hatcher <[EMAIL PROTECTED]> >> wrote: >>> On Dec 5, 2007, at 5:12 AM, Erik Hatcher wrote: >>>> In my perusal of the code (SimpleFacets#getFacetQueryCounts), I'm >>>> not seeing that facet.query respects facet.limit even. If you >>>> asked for a count for a query, you get it regardless of any other >>>> parameters such as mincount or limit. >>> >>> sorry, facet.limit doesn't make sense for a facet.query.... what I >>> meant was that it doesn't support mincount. >> >> Right... in most cases I don't think mincount really makes sense for a >> facet.query either. > > I agree with that as well. If you ask for a count for a query, you > get it regardless of whether it is zero or not. You asked for it, > you got it! > > Erik > > > -- View this message in context: http://www.nabble.com/possible-to-set-mincount-on-facetquery--tf4948462.html#a14176570 Sent from the Solr - User mailing list archive at Nabble.com.
