[
https://issues.apache.org/jira/browse/LUCENE-6393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14396004#comment-14396004
]
Paul Elschot edited comment on LUCENE-6393 at 4/4/15 11:42 PM:
---------------------------------------------------------------
Lots of deleted lines, good sign.
For migrating this logic I think one step at a time should work. Let's see what
the other Span queries need for two phase iteration.
The others are SpanOr/MultiTerm and PayloadTermQuery, or did I miss one?
was (Author: [email protected]):
Lots of deleted lines, good sign.
For migrating this logic I think one step at a time should work. Let's see what
the remaining Span queries need for two phase iteration.
The others are SpanOr/MultiTerm and PayloadTermQuery, or did I miss one?
> SpanFirstQuery sometimes returns Spans without any positions
> ------------------------------------------------------------
>
> Key: LUCENE-6393
> URL: https://issues.apache.org/jira/browse/LUCENE-6393
> Project: Lucene - Core
> Issue Type: Bug
> Reporter: Robert Muir
> Fix For: Trunk, 5.2
>
> Attachments: LUCENE-6393-alternative.patch, LUCENE-6393.patch,
> LUCENE-6393.patch, LUCENE-6393.patch
>
>
> This hits an assert in SpanScorer because it breaks the javadocs contract of
> Spans.nextStartPosition():
> * Returns the next start position for the current doc.
> * There is always *at least one start/end position* per doc.
> * After the last start/end position at the current doc this returns
> NO_MORE_POSITIONS.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
