Note that any multivalued fields that rely on the data being returned in the same order it was added will break since MV fields are returned in sorted order when they're DV fields. Probably an edge case, but still.... On Mar 7, 2016 08:06, "Ishan Chattopadhyaya (JIRA)" <[email protected]> wrote:
> > [ > https://issues.apache.org/jira/browse/SOLR-8740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15183190#comment-15183190 > ] > > Ishan Chattopadhyaya commented on SOLR-8740: > -------------------------------------------- > > In the same breath, now that non-stored docValues fields can be accessed > through the docValues api, I think the version field should be non-stored > dv going forward. SOLR-6337 > > > use docValues by default > > ------------------------ > > > > 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 > > > > > > We should consider switching to docValues for most of our non-text > fields. 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] > >
