[
https://issues.apache.org/jira/browse/SOLR-8740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15185031#comment-15185031
]
Yonik Seeley commented on SOLR-8740:
------------------------------------
bq. The issue here which Yonik created is about making docValues as default. So
even if you don't mark a field explicitly with docValues="true" in your schema
, Solr will enable it.
Oh, hmmm, that's a good point. I hadn't actually meant that. But I now
realize that the issue title/description is somewhat ambiguous.
As an example, 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.
If we can set docValues=true on a fieldType and have it carry over to all
fields by default, then that's even friendly for fields added via API or
guessed fields.
> 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]
