lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yonik Seeley (JIRA)" <>
Subject [jira] Commented: (LUCENE-1974) BooleanQuery can not find all matches in special condition
Date Wed, 14 Oct 2009 00:25:31 GMT


Yonik Seeley commented on LUCENE-1974:

bq. It's also concerning that no unit test catches this... 

I've said it before, I'll say it again... anything of sufficient complexity really benefits
from random tests to hit boundary cases that one would not have thought to code for.  We have
quite a few in Solr, but not enough.  We obviously don't have enough in Lucene either.

One other simple tactic I've used in Solr to increase the chance of hitting boundary conditions
is to make sure many segments are created by default (bad for performance, good for testing),
and that cache sizes, window sizes, etc are small so that they are crossed more often by more

> BooleanQuery can not find all matches in special condition
> ----------------------------------------------------------
>                 Key: LUCENE-1974
>                 URL:
>             Project: Lucene - Java
>          Issue Type: Bug
>          Components: Query/Scoring
>    Affects Versions: 2.9
>            Reporter: tangfulin
>            Assignee: Michael McCandless
>             Fix For: 2.9.1, 3.0
>         Attachments:, LUCENE-1974.test.patch, LUCENE-1974.test.patch
> query: (name:tang*)
> doc=5137 score=1.0  doc:Document<stored,indexed<name:tangfulin>>
> doc=11377 score=1.0  doc:Document<stored,indexed<name:tangfulin>>
> query: name:tang* name:notexistnames
> doc=5137 score=0.048133932  doc:Document<stored,indexed<name:tangfulin>>
> It is two queries on the same index, one is just a prefix query in a
> boolean query, and the other is a prefix query plus a term query in a
> boolean query, all with Occur.SHOULD .
> what I wonder is why the later query can not find the doc=11377 doc ?
> the problem can be repreduced by the code in the attachment .

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

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message