You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@lucene.apache.org by "Michele Palmia (Jira)" <ji...@apache.org> on 2020/03/02 23:14:00 UTC

[jira] [Commented] (LUCENE-9258) DocTermsIndexDocValues should not assume it's operating on a SortedDocValues field

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

Michele Palmia commented on LUCENE-9258:
----------------------------------------

I added a patch with the fix together with a(n addition to a) test that fails with the current implementation. Any advice on improving the testing would be greatly appreciated (is it ok to test the Scorer independently? Should I mock the Weight?).

> DocTermsIndexDocValues should not assume it's operating on a SortedDocValues field
> ----------------------------------------------------------------------------------
>
>                 Key: LUCENE-9258
>                 URL: https://issues.apache.org/jira/browse/LUCENE-9258
>             Project: Lucene - Core
>          Issue Type: Bug
>    Affects Versions: 8.4
>            Reporter: Michele Palmia
>            Priority: Minor
>         Attachments: LUCENE-9258.patch
>
>
> When requesting a new _ValueSourceScorer_ (with _getRangeScorer_) from _DocTermsIndexDocValues_ , the latter instantiates a new iterator on _SortedDocValues_ regardless of the fact that the underlying field can actually be of a different type (e.g. a _SortedSetDocValues_ processed through a _SortedSetSelector_).



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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