[
https://issues.apache.org/jira/browse/SOLR-10437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15960106#comment-15960106
]
Hoss Man commented on SOLR-10437:
---------------------------------
Argh... sorry tomas: i was so heads down in Points it didn't occur to me to
check if this was the (intentional) behavior of all fields.
Your suggested test fixes seem fine ... personally I'd prefer if, for each
field, the "caller" passed in a boolean indicating wether they expected the
field to be returned when explicitly included in the "fl" (rather hen asking
the schema if the field has docValues) because that helps protect us against
someone down the road changing the schema (ie: make everything have docValues
by default) and reducing our test coverage ... but It's probably not that big
of a deal (and you already wrote this version)
(FYI: your second patch seems to depend on the first?)
Should we resolve:invalid this issue & commit your patch as an addendum of
SOLR-10425 since it's really just fixing the (defective by design) test i wrote
there?
> Field retrieved from DocValues even if useDocValuesAsStored=false when
> included in fl parameter
> -----------------------------------------------------------------------------------------------
>
> Key: SOLR-10437
> URL: https://issues.apache.org/jira/browse/SOLR-10437
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Hoss Man
> Assignee: Tomás Fernández Löbbe
> Attachments: SOLR-10437.patch, SOLR-10437.patch
>
>
> As pat of the tests we're adding for SOLR-10425 we noticed that (at first
> glance) useDocValuesAsStored=false doesn't seem to be working for
> PointsFields -- but it seems unrelated to the root of that issue, so we're
> spinning this off for futher investigation.
> patches/commits for SOLR-10425 will include a disabled test refering to this
> jira which can be enabled to see the problem
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
