[
https://issues.apache.org/jira/browse/LUCENE-6226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14314142#comment-14314142
]
Robert Muir commented on LUCENE-6226:
-------------------------------------
{quote}
I'm not sure about dropping offsets from the enum though. We don't have
anything that uses them now, but one of the reasons for doing this is so that
we can add a highlighter that iterates through the positions from a scorer, and
that will need to use offsets.
{quote}
Another way LUCENE-2878 fails is it tries to serve two masters:
1) improve positional queries
2) add stuff to the search api to help highlighters.
By doing this, performance suffered.
I am convinced that we should not do #2. Our core search apis are already too
complicated. Highlighters can "deal" with whatever we throw at them ultimately,
or continue working how they are working today. We should have a razor sharp
focus on #1 and only do what is minimal and necessary to support core search
queries better.
> 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, LUCENE-6226.patch,
> 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]