[
https://issues.apache.org/jira/browse/LUCENE-6226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14312144#comment-14312144
]
Robert Muir commented on LUCENE-6226:
-------------------------------------
But we just need to figure out the semantics of the API. I don't think the API
shoudl be an afterthought.
Again my primary example is the phrase scorers here, they seem to be turning on
positions regardless. But I don't know why they would do this, since this
should be about what is exposed on the scorer itself.
In other words, i can get a phrase scorer that is DOCS_ONLY. and today this is
what happens when needsScores=false, we only consume docids, hence we don't
care about freq() on the scorer, and it means we can do much less phrase
matching (just find the first matching phrase) in these situations.
We need to make sure semantics make sense with the new API.
> 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
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
