On Thu, Apr 25, 2013 at 12:35 AM, Toke Eskildsen <t...@statsbiblioteket.dk>wrote:
> > > > This leads me to believe that the FQ is being applied AFTER the facets > are > > calculated on the whole data set. For my use case it would make a ton of > > sense to apply the FQ first and then facet. Is it possible to specify > this > > behavior or do I need to get into the code and get my hands dirty? > > > As for creating a new faceting implementation that avoids the startup > penalty by using only the found documents, then it is technically quite > simple: Use stored fields, iterate the hits and request the values. > Unfortunately this scales poorly with the number of hits, so unless you > can guarantee that you will always have small result sets, this is > probably not a viable option. > > Thank you Toke for your detailed reply. I have perhaps an unusual use case where we may have hundreds of thousands of users each with a few thousand documents. On some queries I can guarantee the result size will be small compared to the entire corpus since I'm filtering on one user's documents. I may give this alternative faceting implementation a try. Best regards, Daniel
