That's correct, I haven't checked the internals for this one, but as far as I know, it only applies to places where docValues is not explicitly set. I agree with your understanding.
Cheers -------------------------- *Alessandro Benedetti* Director @ Sease Ltd. *Apache Lucene/Solr Committer* *Apache Solr PMC Member* e-mail: a.benede...@sease.io *Sease* - Information Retrieval Applied Consulting | Training | Open Source Website: Sease.io <http://sease.io/> LinkedIn <https://linkedin.com/company/sease-ltd> | Twitter <https://twitter.com/seaseltd> | Youtube <https://www.youtube.com/channel/UCDx86ZKLYNpI3gzMercM7BQ> | Github <https://github.com/seaseltd> On Tue, 17 Sept 2024 at 23:39, Kevin Liang (BLOOMBERG/ 919 3RD A) < klian...@bloomberg.net> wrote: > Per the solr 9.7 release notes, docValues are now enabled by default for a > variety of fieldTypes. There is a warning that any index that is not > already using docValues cannot be converted to docValues by Lucene > standard. I want to be absolutely sure that my understanding of what this > means is clear before potentially corrupting the index of my cloud. If I am > understanding this change correctly, the ONLY situation which would require > a re-index is if I have a field & fieldType combination that uses one of > the aforementioned solr primitive fieldTypes and does not have docValues > set correct? > > Some cases: > * docValue is set (true or false) for a field means this field is ok > * docValue is not set for a field, but is set for its fieldType means this > field is ok (as it inherits docValue behavior from fieldType?) > * dynamic fields that fall into one of the previous two cases are ok > > Can someone, or multiple people, help confirm this understanding? Thanks > > -Kevin
