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

Tomás Fernández Löbbe commented on SOLR-8740:
---------------------------------------------

Also, if we add PointFields (SOLR-8396), we'll need docValues for 
sorting/faceting on them. A basic/unoptimized schema would allow you to sort or 
facet on any of those fields as you can do now with TrieFields and the 
FieldCache/FieldValueCache. Later you can optimize the schema by removing DV 
from the fields where you don't need them. I believe that would be a better 
starting experience than not adding DV and giving errors. 

{quote}
I was thinking of things like changing the *_i dynamic field in our schema 
templates to explicitly include docValues="true" by default (or setting it on 
the fieldType if that's a flag that carries over to all of it's fields by 
default).

We could consider changing the default such that even if it doesn't appear in 
the schema, docValues would be true (and bump the schema version of course). I 
had assumed that might be more controversial though, so was just looking to 
effectively change the de-facto defaults.
{quote}

I'm OK either way, I do think in any case we should leave the 
{{docValues="true"}} in the schema to make it more obvious that you want to 
look at that attribute for optimizing your schema. 

> 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