[
https://issues.apache.org/jira/browse/LUCENE-1974?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12765327#action_12765327
]
Michael McCandless commented on LUCENE-1974:
--------------------------------------------
bq. It's also concerning that no unit test catches this...
I agree.... I'll commit tangfulin & Hoss's test case.
I think the other tests do not catch it because the error only happens if the
docID is over 8192 (the chunk size that BooleanScorer uses). Most of our tests
work on smaller sets of docs.
> BooleanQuery can not find all matches in special condition
> ----------------------------------------------------------
>
> Key: LUCENE-1974
> URL: https://issues.apache.org/jira/browse/LUCENE-1974
> Project: Lucene - Java
> Issue Type: Bug
> Components: Query/Scoring
> Affects Versions: 2.9
> Reporter: tangfulin
> Assignee: Michael McCandless
> Attachments: BooleanQueryTest.java, 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: java-dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: java-dev-h...@lucene.apache.org
