Jamai - what is your q= set to? And do you have a fq for the original query? I have found that if you do a wildcard search (*.*) you have to be careful about other parameters you set as that can often result in the numbers returned being off. In my case, my defaults had things like edismax settings for phrase boosting, etc. that don't apply if there isn't a search term, and once I removed those for a wildcard search I got the correct numbers. So possibly your facet query itself may be set up correctly but something else in the parameters and/or filters with the two queries may be the cause of the difference.
Mary Jo On Thu, Jun 2, 2016 at 1:47 PM, Jamal, Sarfaraz < sarfaraz.ja...@verizonwireless.com.invalid> wrote: > Hello Everyone, > > I am working on implementing some basic faceting into my project. > > I have it working the way I want to, but I feel like there is probably a > better way the way I went about it. > > * I want to show a category and its count. > * when someone clicks a category, it sets a FQ= to that category. > > But now that the results are being filtered, the category counts from the > original query without the filters are off. > > So, I have a single api call that I make with rows set to 0 and the base > query without any filters, and use that to display my categories. > > And then I call the api again, this time to get the results. And the > category count is the same. > > I hope that makes sense. > > I was hoping facet.query would be of help, but I am not sure I understood > it properly. > > Thanks in advance =) > > Sas >
