[
https://issues.apache.org/jira/browse/LUCENE-3451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe Schindler updated LUCENE-3451:
----------------------------------
Attachment: LUCENE-3451.patch
Simple patch for trunk:
- Disables the default full-1 bitset if no required/optional clauses
- Moves the Prohibited clauses at the end. The order is now: SHOULD, MUST,
MUST_NOT; I am not sure if this is correct and conforms to BooleanScorer2 (I
don't understand BooleanScorer2). Does somebody know in which order clauses are
applied in BooleanScorer2?
> Remove special handling of pure negative Filters in BooleanFilter
> (inconsistentToBQ+broken)
> -------------------------------------------------------------------------------------------
>
> Key: LUCENE-3451
> URL: https://issues.apache.org/jira/browse/LUCENE-3451
> Project: Lucene - Java
> Issue Type: Bug
> Reporter: Uwe Schindler
> Assignee: Uwe Schindler
> Fix For: 4.0
>
> Attachments: LUCENE-3451.patch
>
>
> We should at least in Lucene 4.0 remove the hack in BooleanFilter that allows
> pure negative Filter clauses. This is not supported by BooleanQuery and
> confuses users (I think that's the problem in LUCENE-3450).
> The hack is buggy, as it does not respect deleted documents and returns them
> in its DocIdSet.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
