[ 
https://issues.apache.org/jira/browse/SOLR-8740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15183357#comment-15183357
 ] 

Adrien Grand commented on SOLR-8740:
------------------------------------

bq. And default to docValuesFormat="Memory" as well, or is that already the 
default when docValues="true" is set?

Having the default setup not using the default codec looks dangerous to me as 
it means that users won't be able to upgrade clusters without switching back to 
the default codec first (which is the only supported one for backwards 
compatibility).

bq.  I've never been able to figure out why Lucene still needs Stored fields 
(other than for tokenized text fields) if docValues is so much better.

Doc values are not better, they just have different trade-offs: stored fields 
are optimized for randomly getting several values from a couple dozen documents 
while doc values are optimized for sequentially reading a couple values from 
many documents. If you were to replace stored fields with doc values, 
performance would become horrible if your index is significantly larger than 
your filesystem cache, especially if you have spinning disks. I suspect it 
could be fine if it was only done for the version field as suggested above but 
doing it for all fields sounds dangerous to me.

> 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]

Reply via email to