[
https://issues.apache.org/jira/browse/SOLR-8344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15034126#comment-15034126
]
Erick Erickson commented on SOLR-8344:
--------------------------------------
Yeah, removed that all from 8220, thought about it more and saw this ticket...
We do want to keep in mind though that from a _user_ perspective, inputting
'2.178734872984723984729387" as a float and getting back "2.17873477935791"
are not equivalent. So whatever we do needs to take that into account. If we
use the stored=docvalues approach, then they'd need a copyField with
stored=true field if it was important to them.
The other thing I like about the stored=docvalues approach, existing
schemas/applications continue to work exactly as they do now. Upgrading is not
surprising. Users can selectively take advantage of this new capability.
I think it'd even work if a user changed an existing schema from stored=true to
stored=docvalues and did not re-index. True, they'd be carrying around some
useless data in the *.fdt files until it was merged away for updated docs, but
as long as docValues=true was set in the original schema, it'd "do the expected
thing".
I suppose the same functionality could come from a new parameter on a <field>
definition like fl_from_dv=true but aside from the awkward name, I think this
is harder to wrap your head around.
If you were willing to pay the "wasted disk space" penalty though, a separate
parameter on the <field> to control where the "stored" value came from would
allow one to switch back and forth without re-indexing. But to be clear, I
don't think this is a good idea; using the stored=docvalues option forces a
decision to be made up-front.
> Decide default when requested fields are both column and row stored.
> --------------------------------------------------------------------
>
> Key: SOLR-8344
> URL: https://issues.apache.org/jira/browse/SOLR-8344
> Project: Solr
> Issue Type: New Feature
> Reporter: Ishan Chattopadhyaya
>
> This issue was discussed in the comments at SOLR-8220. Splitting it out to a
> separate issue so that we can have a focused discussion on whether/how to do
> this.
> If a given set of requested fields are all stored and have docValues (column
> stored), we can retrieve the values from either place. What should the
> default be?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
