OK, it should be fixed now. There was a bug in the TermQuery set generation code.
-Yonik http://www.lucidimagination.com On Wed, May 27, 2009 at 8:46 AM, Yonik Seeley <yo...@lucidimagination.com> wrote: > On Wed, May 27, 2009 at 8:37 AM, Ryan McKinley <ryan...@gmail.com> wrote: >> I am seeing a behavior I have not seen before.... >> >> With all standard queries (nothing custom etc), I will see a facet list with >> items like: >> * valueA (13) >> * valueB (100) >> * etc... >> >> Then when I select valueA (that should have 13 results) I only get 2 >> results. When the index is optimized, it appears to work as expected. > > Is this with the trunk today? > I'll see if I can reproduce with the example data. > > -Yonik >
