[
https://issues.apache.org/jira/browse/LUCENE-6226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14371038#comment-14371038
]
Alan Woodward commented on LUCENE-6226:
---------------------------------------
At the moment, IntervalScorer uses the same algorithm as SpanScorer - calculate
a sloppy freq using the width of each top-level interval, sum them up, and pass
that to SimScorer.score(). It would be interesting to look at other
possibilities, but I think that should be done in a separate issue?
> Add interval iterators to Scorer
> --------------------------------
>
> Key: LUCENE-6226
> URL: https://issues.apache.org/jira/browse/LUCENE-6226
> Project: Lucene - Core
> Issue Type: Improvement
> Reporter: Alan Woodward
> Assignee: Alan Woodward
> Fix For: Trunk, 5.1
>
> Attachments: LUCENE-6226.patch, LUCENE-6226.patch, LUCENE-6226.patch,
> LUCENE-6226.patch, LUCENE-6226.patch, LUCENE-6226.patch, LUCENE-6226.patch
>
>
> This change will allow Scorers to expose which positions within a document
> they have matched, via a new IntervalIterator interface. Consumers get the
> iterator by calling intervals() on the Scorer, then call reset(docId)
> whenever the scorer has advanced and nextInterval() to iterate through
> positions. Once all matching intervals on the current document have been
> exhausted, nextInterval() returns false.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
