: I realized, that the facets are build out of the whole index, not the : subset : returned by the initial query. Therefore I have a large number of empty : facets which I simply ignore. In my case the QueryTime is somewhat
facet.mincount is a way to tell solr not to bother giving you those 0 counts ... you sill still get the name of hte field though so that you know it tried it. : Faceting on manufacturers and categories first and than present the : corresponding facets might be used under some circumstances, but in my case : the category structure is quite deep, detailed and complex. So when : the user enters a query I like to say to him "Look, here are the : manufacturers and categories with matches to your query, choose one if you : want, but maybe there is another one with products that better fit your : needs or products that you didn't even know about. So maybe you like to : filter based on the following attributes." Something like this ;o) categories was just an example i used because it tends to be a common use case ... my point is the decision about which facet qualifies for the "maybe there is another one with products that better fit your needs" part of the response either requires computing counts for *every* facet constraint and then looking at them to see which ones provide good distribution, or by knowing something more about your metadata (ie: having stats that show the majority of people who search on the word "canon" want to facet on "megapixels") .. this is where custom biz logic comes in, becuase in a lot of situations computing counts for every possible facet may not be practical (even if the syntax to request it was easier) -Hoss
