[
https://issues.apache.org/jira/browse/LUCENE-6226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14314138#comment-14314138
]
Robert Muir commented on LUCENE-6226:
-------------------------------------
{quote}
And this way Scorers that don't support positions (or that don't make sense to
return them) are dealt with naturally.
{quote}
I'm not sure its natural, or even correct? Because as far as i could tell, the
idea with LUCENE-2878 issue is that you would have more flexibility as far as
how positions are used in queries. so then why shouldnt it be correct for
MatchAllDocsQuery to return all possible positions from all terms in all
documents? (I'm not actually suggesting this, I'm just hinting that the whole
scheme needs to be figured out before we add even *one* method to support it).
> 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: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
