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 "Renata Perkowska (JIRA)" <ji...@apache.org> on 2009/10/16 11:33:31 UTC

[jira] Created: (SOLR-1514) Facet search results contain 0:0 entries although '0' values were not indexed.

Facet search results contain 0:0 entries although '0' values were not indexed.
------------------------------------------------------------------------------

                 Key: SOLR-1514
                 URL: https://issues.apache.org/jira/browse/SOLR-1514
             Project: Solr
          Issue Type: Bug
          Components: search
    Affects Versions: 1.3
         Environment: Solr is on: Linux  2.6.18-92.1.13.el5xen
            Reporter: Renata Perkowska


Hi,
in my Jmeter  ATs  I can see that under some circumstances facet search results contain '0' both as keys
and values for the integer field called 'year' although I never index zeros. 

When I do a normal search, I don't see any indexed fields with zeros. 

When I run my facet test (using JMeter) in isolation, everything works fine. It happens only when it's being run after other tests
(and other indexing/deleting). On the other hand it shouldn't be the case that other indexing are influencing this test, as at the end of each test I'm deleting
indexed documents so before running the facet test an index is empty.

My facet test looks as follows:
 1. Index group of documents
 2. Perform search on facets
 3. Remove documents from the index.

The results that I'm getting for an integer field 'year':

 1990:4
 1995:4
 0:0
 1991:0
 1992:0
 1993:0
 1994:0
 1996:0
 1997:0
 1998:0

I'm indexing only values 1990-1999, so there certainly shouldn't be any '0'  as keys in the result set.

The indexed is being optimized not after each document deletion from and index, but only when an index is loaded/unloaded, so the optimization won't solve the problem in this case. 
If the facet.mincount is provided, then  I'm not getting 0:0, but other entries with '0' values are gone as well:

1990:4
1995:4


-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (SOLR-1514) Facet search results contain 0:0 entries although '0' values were not indexed.

Posted by "Renata Perkowska (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/SOLR-1514?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Renata Perkowska updated SOLR-1514:
-----------------------------------

    Description: 
Hi,
in my Jmeter  ATs  I can see that under some circumstances facet search results contain '0' both as keys
and values for the integer field called 'year' although I never index zeros. 

When I do a normal search, I don't see any indexed fields with zeros. 

When I run my facet test (using JMeter) in isolation, everything works fine. It happens only when it's being run after other tests
(and other indexing/deleting). On the other hand it shouldn't be the case that other indexing are influencing this test, as at the end of each test I'm deleting
indexed documents so before running the facet test an index is empty.

My facet test looks as follows:
 1. Index group of documents
 2. Perform search on facets
 3. Remove documents from the index.

The results that I'm getting for an integer field 'year':

 1990:4
 1995:4
 0:0
 1991:0
 1992:0
 1993:0
 1994:0
 1996:0
 1997:0
 1998:0

I'm indexing only values 1990-1999, so there certainly shouldn't be any '0'  as keys in the result set.

The indexed is being optimized not after each document deletion from and index, but only when an index is loaded/unloaded, so the optimization won't solve the problem in this case. 
If the facet.mincount>0 is provided, then  I'm not getting 0:0, but other entries with '0' values are gone as well:

1990:4
1995:4


  was:
Hi,
in my Jmeter  ATs  I can see that under some circumstances facet search results contain '0' both as keys
and values for the integer field called 'year' although I never index zeros. 

When I do a normal search, I don't see any indexed fields with zeros. 

When I run my facet test (using JMeter) in isolation, everything works fine. It happens only when it's being run after other tests
(and other indexing/deleting). On the other hand it shouldn't be the case that other indexing are influencing this test, as at the end of each test I'm deleting
indexed documents so before running the facet test an index is empty.

My facet test looks as follows:
 1. Index group of documents
 2. Perform search on facets
 3. Remove documents from the index.

The results that I'm getting for an integer field 'year':

 1990:4
 1995:4
 0:0
 1991:0
 1992:0
 1993:0
 1994:0
 1996:0
 1997:0
 1998:0

I'm indexing only values 1990-1999, so there certainly shouldn't be any '0'  as keys in the result set.

The indexed is being optimized not after each document deletion from and index, but only when an index is loaded/unloaded, so the optimization won't solve the problem in this case. 
If the facet.mincount is provided, then  I'm not getting 0:0, but other entries with '0' values are gone as well:

1990:4
1995:4



> Facet search results contain 0:0 entries although '0' values were not indexed.
> ------------------------------------------------------------------------------
>
>                 Key: SOLR-1514
>                 URL: https://issues.apache.org/jira/browse/SOLR-1514
>             Project: Solr
>          Issue Type: Bug
>          Components: search
>    Affects Versions: 1.3
>         Environment: Solr is on: Linux  2.6.18-92.1.13.el5xen
>            Reporter: Renata Perkowska
>
> Hi,
> in my Jmeter  ATs  I can see that under some circumstances facet search results contain '0' both as keys
> and values for the integer field called 'year' although I never index zeros. 
> When I do a normal search, I don't see any indexed fields with zeros. 
> When I run my facet test (using JMeter) in isolation, everything works fine. It happens only when it's being run after other tests
> (and other indexing/deleting). On the other hand it shouldn't be the case that other indexing are influencing this test, as at the end of each test I'm deleting
> indexed documents so before running the facet test an index is empty.
> My facet test looks as follows:
>  1. Index group of documents
>  2. Perform search on facets
>  3. Remove documents from the index.
> The results that I'm getting for an integer field 'year':
>  1990:4
>  1995:4
>  0:0
>  1991:0
>  1992:0
>  1993:0
>  1994:0
>  1996:0
>  1997:0
>  1998:0
> I'm indexing only values 1990-1999, so there certainly shouldn't be any '0'  as keys in the result set.
> The indexed is being optimized not after each document deletion from and index, but only when an index is loaded/unloaded, so the optimization won't solve the problem in this case. 
> If the facet.mincount>0 is provided, then  I'm not getting 0:0, but other entries with '0' values are gone as well:
> 1990:4
> 1995:4

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Commented: (SOLR-1514) Facet search results contain 0:0 entries although '0' values were not indexed.

Posted by "Hoss Man (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/SOLR-1514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12767890#action_12767890 ] 

Hoss Man commented on SOLR-1514:
--------------------------------

Can you provide a JUnit test case, or a schema.xml + some sample docs that reproduce this behavior?

> Facet search results contain 0:0 entries although '0' values were not indexed.
> ------------------------------------------------------------------------------
>
>                 Key: SOLR-1514
>                 URL: https://issues.apache.org/jira/browse/SOLR-1514
>             Project: Solr
>          Issue Type: Bug
>          Components: search
>    Affects Versions: 1.3
>         Environment: Solr is on: Linux  2.6.18-92.1.13.el5xen
>            Reporter: Renata Perkowska
>
> Hi,
> in my Jmeter  ATs  I can see that under some circumstances facet search results contain '0' both as keys
> and values for the integer field called 'year' although I never index zeros. 
> When I do a normal search, I don't see any indexed fields with zeros. 
> When I run my facet test (using JMeter) in isolation, everything works fine. It happens only when it's being run after other tests
> (and other indexing/deleting). On the other hand it shouldn't be the case that other indexing are influencing this test, as at the end of each test I'm deleting
> indexed documents so before running the facet test an index is empty.
> My facet test looks as follows:
>  1. Index group of documents
>  2. Perform search on facets
>  3. Remove documents from the index.
> The results that I'm getting for an integer field 'year':
>  1990:4
>  1995:4
>  0:0
>  1991:0
>  1992:0
>  1993:0
>  1994:0
>  1996:0
>  1997:0
>  1998:0
> I'm indexing only values 1990-1999, so there certainly shouldn't be any '0'  as keys in the result set.
> The indexed is being optimized not after each document deletion from and index, but only when an index is loaded/unloaded, so the optimization won't solve the problem in this case. 
> If the facet.mincount>0 is provided, then  I'm not getting 0:0, but other entries with '0' values are gone as well:
> 1990:4
> 1995:4
> I'm also indexing text fields, but I don't see a similar situation in this case. This bug only happens for integer fields.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (SOLR-1514) Facet search results contain 0:0 entries although '0' values were not indexed.

Posted by "Renata Perkowska (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/SOLR-1514?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Renata Perkowska updated SOLR-1514:
-----------------------------------

    Description: 
Hi,
in my Jmeter  ATs  I can see that under some circumstances facet search results contain '0' both as keys
and values for the integer field called 'year' although I never index zeros. 

When I do a normal search, I don't see any indexed fields with zeros. 

When I run my facet test (using JMeter) in isolation, everything works fine. It happens only when it's being run after other tests
(and other indexing/deleting). On the other hand it shouldn't be the case that other indexing are influencing this test, as at the end of each test I'm deleting
indexed documents so before running the facet test an index is empty.

My facet test looks as follows:
 1. Index group of documents
 2. Perform search on facets
 3. Remove documents from the index.

The results that I'm getting for an integer field 'year':

 1990:4
 1995:4
 0:0
 1991:0
 1992:0
 1993:0
 1994:0
 1996:0
 1997:0
 1998:0

I'm indexing only values 1990-1999, so there certainly shouldn't be any '0'  as keys in the result set.

The indexed is being optimized not after each document deletion from and index, but only when an index is loaded/unloaded, so the optimization won't solve the problem in this case. 
If the facet.mincount>0 is provided, then  I'm not getting 0:0, but other entries with '0' values are gone as well:

1990:4
1995:4

I'm also indexing text fields, but I don't see a similar situation in this case. This bug only happens for integer fields.


  was:
Hi,
in my Jmeter  ATs  I can see that under some circumstances facet search results contain '0' both as keys
and values for the integer field called 'year' although I never index zeros. 

When I do a normal search, I don't see any indexed fields with zeros. 

When I run my facet test (using JMeter) in isolation, everything works fine. It happens only when it's being run after other tests
(and other indexing/deleting). On the other hand it shouldn't be the case that other indexing are influencing this test, as at the end of each test I'm deleting
indexed documents so before running the facet test an index is empty.

My facet test looks as follows:
 1. Index group of documents
 2. Perform search on facets
 3. Remove documents from the index.

The results that I'm getting for an integer field 'year':

 1990:4
 1995:4
 0:0
 1991:0
 1992:0
 1993:0
 1994:0
 1996:0
 1997:0
 1998:0

I'm indexing only values 1990-1999, so there certainly shouldn't be any '0'  as keys in the result set.

The indexed is being optimized not after each document deletion from and index, but only when an index is loaded/unloaded, so the optimization won't solve the problem in this case. 
If the facet.mincount>0 is provided, then  I'm not getting 0:0, but other entries with '0' values are gone as well:

1990:4
1995:4



> Facet search results contain 0:0 entries although '0' values were not indexed.
> ------------------------------------------------------------------------------
>
>                 Key: SOLR-1514
>                 URL: https://issues.apache.org/jira/browse/SOLR-1514
>             Project: Solr
>          Issue Type: Bug
>          Components: search
>    Affects Versions: 1.3
>         Environment: Solr is on: Linux  2.6.18-92.1.13.el5xen
>            Reporter: Renata Perkowska
>
> Hi,
> in my Jmeter  ATs  I can see that under some circumstances facet search results contain '0' both as keys
> and values for the integer field called 'year' although I never index zeros. 
> When I do a normal search, I don't see any indexed fields with zeros. 
> When I run my facet test (using JMeter) in isolation, everything works fine. It happens only when it's being run after other tests
> (and other indexing/deleting). On the other hand it shouldn't be the case that other indexing are influencing this test, as at the end of each test I'm deleting
> indexed documents so before running the facet test an index is empty.
> My facet test looks as follows:
>  1. Index group of documents
>  2. Perform search on facets
>  3. Remove documents from the index.
> The results that I'm getting for an integer field 'year':
>  1990:4
>  1995:4
>  0:0
>  1991:0
>  1992:0
>  1993:0
>  1994:0
>  1996:0
>  1997:0
>  1998:0
> I'm indexing only values 1990-1999, so there certainly shouldn't be any '0'  as keys in the result set.
> The indexed is being optimized not after each document deletion from and index, but only when an index is loaded/unloaded, so the optimization won't solve the problem in this case. 
> If the facet.mincount>0 is provided, then  I'm not getting 0:0, but other entries with '0' values are gone as well:
> 1990:4
> 1995:4
> I'm also indexing text fields, but I don't see a similar situation in this case. This bug only happens for integer fields.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.