[
https://issues.apache.org/jira/browse/SOLR-8740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15233140#comment-15233140
]
Ishan Chattopadhyaya commented on SOLR-8740:
--------------------------------------------
[[email protected]], in the Solr 6.0 release notes, the following was mentioned:
{code}
Users should set useDocValuesAsStored="false" to preserve sort order on
multi-valued
fields that have both stored="true" and docValues="true".
{code}
Given that useDocValuesAsStored doesn't *currently* affect fields with
stored=true, do you think this note was appropriately worded? I agree that in
future, we might have useDocValuesAsStored affect how we retrieve stored=true
fields, but whether that will affect the ordering is still not known (since we
can, in theory, use another docValues format that preserves the original
order). Though, even if future optimizations are potentially breaking for a
user, the note mentioned above implies something that needs to be done for
avoiding a current issue, not a future issue.
> set docValues="true" for most non-text fieldTypes in the sample schemas
> -----------------------------------------------------------------------
>
> Key: SOLR-8740
> URL: https://issues.apache.org/jira/browse/SOLR-8740
> Project: Solr
> Issue Type: Improvement
> Affects Versions: master
> Reporter: Yonik Seeley
> Fix For: master, 6.0
>
> Attachments: SOLR-8740.patch, SOLR-8740.patch
>
>
> We should consider switching to docValues for most of the non-text fields in
> the sample schemas provided with solr.
> This may be a better default since it is more NRT friendly and acts to avoid
> OOM errors due to large field cache or UnInvertedField entries.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
