[LUCENE-6926] Take matchCost into account for MUST_NOT clauses - ASF JIRA

XML

Word

Printable

JSON

Details

Type: Improvement
Status: Closed
Priority: Minor
Resolution: Fixed
Affects Version/s: None
Fix Version/s: 5.5, 6.0
Component/s: None
Labels:
None

Lucene Fields:

New

Description

ReqExclScorer potentially has two TwoPhaseIterators to check: the one for the positive clause and the one for the negative clause. It should leverage the match cost API to check the least costly one first.

Attachments

- Sort By Name
- Sort By Date
- Ascending
- Descending

LUCENE-6926.patch
14/Dec/15 10:50
7 kB
Adrien Grand
LUCENE-6926.patch
10/Dec/15 19:53
6 kB
Adrien Grand

Activity

People

Assignee:: Adrien Grand

Reporter:: Adrien Grand

Votes:: 0 Vote for this issue

Watchers:: 3 Start watching this issue

Dates

Created:: 10/Dec/15 19:43

Updated:: 28/Aug/22 14:46

Resolved:: 04/Jan/16 16:56