[
https://issues.apache.org/jira/browse/LUCENE-6226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14311933#comment-14311933
]
Alan Woodward commented on LUCENE-6226:
---------------------------------------
Good point on Collector.postingsFlags(), I'll change that back.
The PostingsEnum contract is that you should only call .nextPosition() up to
.freq() times, it doesn't know anything about NO_MORE_POSITIONS. I've gone
back and forth a bit about where this should be dealt with, though. I suppose
the nicest solution would be for NO_MORE_POSITIONS to somehow be encoded
directly into the positions data in the index, so that it's returned naturally
when reading the postings and doesn't require any branching anywhere, but I
need to look more carefully at the index format to see if that's plausible.
What do you think?
> Allow TermScorer to expose positions, offsets and payloads
> ----------------------------------------------------------
>
> 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
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
