[
https://issues.apache.org/jira/browse/SOLR-14821?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17190712#comment-17190712
]
Jason Gerlowski commented on SOLR-14821:
----------------------------------------
Ah, hmm, I can see it locally now - I initially couldn't because I was
specifying {{docValuesTermsFIlter}} but didn't have enough terms for
{{docValuesTermsFilterTopLevel}} to be chosen - which is where the actual
problem is. Trivial to reproduce locally if you specify dVTFTL as your method
directly. The test code I mentioned in my comment above must actually be
multi-valued for {{author_s}}?
In any case your fix is straightforward and correct. Just need to fix the test
up before committing.
> docValuesTermsFilter should support single-valued docValues fields
> ------------------------------------------------------------------
>
> Key: SOLR-14821
> URL: https://issues.apache.org/jira/browse/SOLR-14821
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Components: query parsers
> Reporter: Anatolii Siuniaev
> Assignee: Jason Gerlowski
> Priority: Minor
> Attachments: SOLR-14821.patch
>
>
> SOLR-13890 introduced a post-filter implementation for docValuesTermsFilter
> in TermsQParserPlugin. But now it supports only multi-valued docValues
> fields (i.e. SORTED_SET type DocValues)
> It doesn't work for single-valued docValues fields (i.e. SORTED type
> DocValues), though it should.
--
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
