[
https://issues.apache.org/jira/browse/LUCENE-6226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14369388#comment-14369388
]
Paul Elschot commented on LUCENE-6226:
--------------------------------------
Intervals/spans are produced by proximity queries.
I think intervals/spans need a score value of their own.
These score values can be summed up per doc to something pretty close to what
is now the total (fuzzy) frequency.
For a term, this score value is the current influence on the document score of
a single term occurrence, for example the idf times a query weight.
The question then becomes how proximity queries/scorers produce the score
values of the intervals/spans that they produce from the intervals/spans that
they consume. Which ways/mechanisms do we need for that?
> 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]
