>> Notice how, before the fq clause is added, none of the >> 0-count facets are >> returned, even though facet.mincount = 0, but afterward, a >> bunch of 0-count >> facets are returned? >> > This is normal.
What's behind that? Is it widening the results before the mincount constraint is being applied? > I couldn't fully follow, but you want something like multi-select > faceting? > > http://search-lucene.com/ is an example for that, user can select solr and > lucene from the project facet > at the same time. > > http://wiki.apache.org/solr/SimpleFacetParameters#Multi-Select_Faceting_and_LocalParams No. Search-Lucene actually appears to remove facets when they're not returned. If you select Blue, and Red is eliminated, Red won't show up as a facet anymore. Therefore, the user select Red to add it back into the result set. Multi-selection keeps eliminated facets, but gives them virtual counts related to the entire result set. If you select Blue(32) and Red(10) is eliminated, multi-selection causes Red(10) to be displayed. Therefore, the user can't tell that Red was eliminated, and the Red facet no longer has any connection to the values int the result set. What we need to do is show eliminated facets with a 0 count, so if you select Blue (32) and Red (10) is eliminated, we show Red (0). That indicates that there are zero documents in the result set for Red, but Red can still be selected to add Red documents back into the result set. Thanks -- View this message in context: http://lucene.472066.n3.nabble.com/Adding-fq-to-query-with-mincount-0-causes-unexpected-0-count-facet-values-to-be-returned-tp2236105p2236309.html Sent from the Solr - User mailing list archive at Nabble.com.
