[
https://issues.apache.org/jira/browse/LUCENE-6226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14314095#comment-14314095
]
Robert Muir commented on LUCENE-6226:
-------------------------------------
We need to figure out these semantics. I dont understand why we need to
silently return negative positions if the request doesnt make sense.
As far as "dropping offsets" remember they are not there today. I see this
issue as an attempt to iterate, but iteration means making compromises. As far
as this issue, quickly shoving everything into "just" termscorer isn't
iterating to me, its just doing the job half-way.
So we need to meet in the middle somehow. I'm suggesting dropping offsets for
now, dropping payloads for now, and *just* adding positions to scorer, with
clearly defined semantics about what happens when they aren't supported or
don't make sense as a start. I actually think this is ridiculously complicated
enough.
> 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]
