[
https://issues.apache.org/jira/browse/LUCENE-6226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14314059#comment-14314059
]
Robert Muir commented on LUCENE-6226:
-------------------------------------
Hmm, I am a little confused. I am unsure about this new enum for the low level
postings api (versus scorers).
Realistically, they are different. The new enum is a little bogus in that it
pretends to be comparable, but Offsets and Payloads and All is a mess. I don't
think we should bring this into our postings api? Maybe its ok for Scorer, but
we should keep that contained. I do think its nice to have a unified api across
them, but i don't think our codec api should suffer from "problems" in
scorer-land :)
And I still don't have an understanding of the proposed semantics for scorers.
If I only have documents in the index, but i ask for frequencies, what happens?
If i only have positions and ask for payloads, etc.
It can't really be consistent with postings, which return null in unsupported
cases, since returning null already has a special meaning for Weight.scorer().
> 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]
