You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@lucene.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2018/05/02 13:13:00 UTC

[jira] [Commented] (LUCENE-8142) Should codecs expose raw impacts?

    [ https://issues.apache.org/jira/browse/LUCENE-8142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16460998#comment-16460998 ] 

ASF subversion and git services commented on LUCENE-8142:
---------------------------------------------------------

Commit af680af77f3f80c779e038a0ad8a136c9dcb9f5d in lucene-solr's branch refs/heads/master from [~jpountz]
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=af680af ]

LUCENE-8142: Make postings APIs expose raw impacts rather than scores.


> Should codecs expose raw impacts?
> ---------------------------------
>
>                 Key: LUCENE-8142
>                 URL: https://issues.apache.org/jira/browse/LUCENE-8142
>             Project: Lucene - Core
>          Issue Type: Improvement
>            Reporter: Adrien Grand
>            Priority: Minor
>         Attachments: LUCENE-8142.patch
>
>
> Follow-up of LUCENE-4198. Currently, call-sites of TermsEnum.impacts provide a SimScorer so that the maximum score for the block can be computed. Should ImpactsEnum instead return the (freq,norm) pairs and let callers deal with max score computation?



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org