dsmiley commented on code in PR #3903: URL: https://github.com/apache/solr/pull/3903#discussion_r2749993770
########## solr/solr-ref-guide/modules/configuration-guide/pages/coreadmin-api.adoc: ########## @@ -786,20 +786,16 @@ If the `split.key` parameter is specified then only documents having the same ro The `UPGRADECOREINDEX` action upgrades an existing core's index in-place after a Solr major-version upgrade by reindexing documents from older-format segments. If a core is upgraded by this action, it ensures index compatibility with the next Solr major version (upon a future Solr upgrade) without having to re-create the index from source. -This action is expensive and is intended for installations running Solr in user-managed (or standalone) mode only. It is currently not supported in SolrCloud mode. +This action is expensive and can take a while to complete on large indexes. Consider running with `async` option in such cases. -[NOTE] -==== -Only fields that are stored or have DocValues enabled can be preserved during upgrade. -Fields that are neither stored nor docValues-backed will lose their data. However if a field is neither stored, nor docValues-enabled, but is a copyField target, it will be re-populated by the copy field mechanism during reindexing. -Always test on a copy and ensure you have a backup before running on production data. -==== +Note: -[NOTE] -==== -Indexes containing nested documents (parent-child document hierarchies) are not supported by this action. -If nested documents are detected in the index, the operation will fail with an error. -==== +* Only stored fields and fields with docValues enabled can be preserved during upgrade. +Fields that are neither stored nor docValues-backed will lose their data, unless they are `copyField` targets. +* Not supported in SolrCloud mode. In order to achieve the same purpose in SolrCloud mode (aka upgrade index for compatibility with next Solr version), configure the `LatestVersionMergePolicyFactory` for the collection and reindex all documents through a client utility. +* Indexes containing nested documents (parent-child document hierarchies) are not supported. Review Comment: I suggest: > Indexes containing child / nested documents are not supported. Applies to child docs generally, not limited to nested structure. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
