[
https://issues.apache.org/jira/browse/LUCENE-9258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17053589#comment-17053589
]
David Smiley commented on LUCENE-9258:
--------------------------------------
Makes sense to me; your test is perfect. I'm curious; how did you see this at
a higher level (e.g. Solr or ES)? The issue title & details here are a bit
geeky / low-level and I'm trying to think of a good CHANGES.txt entry that
might be more meaningful to users.
> 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: 7.7.2, 8.4
> Reporter: Michele Palmia
> Assignee: David Smiley
> 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-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
