You are viewing a plain text version of this content. The canonical link for it is here.
Posted to solr-dev@lucene.apache.org by Ryan McKinley <ry...@gmail.com> on 2009/05/27 14:37:52 UTC
facet strangeness in /trunk?
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.
I'm guessing this has something to do with the mass of recent changes.
Any thoughts?
thanks!
ryan
Re: facet strangeness in /trunk?
Posted by Ryan McKinley <ry...@gmail.com>.
from trunk sometime mid-morning yesterday
On May 27, 2009, at 8:46 AM, Yonik Seeley wrote:
> On Wed, May 27, 2009 at 8:37 AM, Ryan McKinley <ry...@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
Re: facet strangeness in /trunk?
Posted by Ryan McKinley <ry...@gmail.com>.
manifest info:
Specification-Version: 1.3.0.2009.05.26.09.08.22
Specification-Vendor: The Apache Software Foundation
Implementation-Title: org.apache.solr
Implementation-Version: 1.4-dev 778686 - ryan - 2009-05-26 09:08:22
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 <ry...@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
>
Re: facet strangeness in /trunk?
Posted by Yonik Seeley <yo...@lucidimagination.com>.
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 <ry...@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
>
Re: facet strangeness in /trunk?
Posted by Yonik Seeley <yo...@lucidimagination.com>.
On Wed, May 27, 2009 at 8:37 AM, Ryan McKinley <ry...@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