[ 
https://issues.apache.org/jira/browse/LUCENE-6226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14371577#comment-14371577
 ] 

Paul Elschot commented on LUCENE-6226:
--------------------------------------

This issue is about adding interval/span iterators to scorer, and I think some 
of the scoring for intervals is better left to the intervals/spans themselves, 
see my previous posts.
I agree that a separate issue for that is better.

I'd like to have the possibity to somehow converge the code at LUCENE-6308 to 
the code here. This is actually also a separate issue, but anyway.
At LUCENE-6308 an interval/spans iterator (SpansEnum) is an extension of 
DocIdSetIterator, mostly because that allows a move away from Spans that is not 
too large.
The IntervalIterator here is an interface that does not have methods directly 
related to doc id set iteration.
So the question is: is there an implementation of the IntervalIterator here 
that is used without the context of a DocIdSetIterator ?


> 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]

Reply via email to