This is an automated email from the ASF dual-hosted git repository.

dsmiley pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/solr.git


The following commit(s) were added to refs/heads/main by this push:
     new b885c8abbb0 SOLR-16924: needn't retain back-compat
b885c8abbb0 is described below

commit b885c8abbb023e1becb9bb1cc12592cb6c9b377d
Author: David Smiley <[email protected]>
AuthorDate: Mon Oct 9 23:41:11 2023 -0300

    SOLR-16924: needn't retain back-compat
---
 solr/CHANGES.txt                                                     | 3 +--
 .../modules/upgrade-notes/pages/major-changes-in-solr-10.adoc        | 5 -----
 .../modules/upgrade-notes/pages/major-changes-in-solr-9.adoc         | 3 +++
 3 files changed, 4 insertions(+), 7 deletions(-)

diff --git a/solr/CHANGES.txt b/solr/CHANGES.txt
index ae63ebfd9ed..9fd248374eb 100644
--- a/solr/CHANGES.txt
+++ b/solr/CHANGES.txt
@@ -73,8 +73,7 @@ New Features
 Improvements
 ---------------------
 * SOLR-16924: RESTORECORE now sets the UpdateLog to ACTIVE state instead of 
requiring a separate
-  REQUESTAPPLYUPDATES call in Collection restore. The latter will still happen 
in 9.x for
-  backwards-compatibility.  (Julia Lamoine, David Smiley)
+  REQUESTAPPLYUPDATES call in Collection restore.  (Julia Lamoine, David 
Smiley)
 
 Optimizations
 ---------------------
diff --git 
a/solr/solr-ref-guide/modules/upgrade-notes/pages/major-changes-in-solr-10.adoc 
b/solr/solr-ref-guide/modules/upgrade-notes/pages/major-changes-in-solr-10.adoc
index b90e1daf6b4..fed3ed14110 100644
--- 
a/solr/solr-ref-guide/modules/upgrade-notes/pages/major-changes-in-solr-10.adoc
+++ 
b/solr/solr-ref-guide/modules/upgrade-notes/pages/major-changes-in-solr-10.adoc
@@ -30,11 +30,6 @@ Before starting an upgrade to this version of Solr, please 
take the time to revi
 
 Starting in 10, the Maven POM for SolrJ does not refer to SolrJ modules like 
ZooKeeper.  If you require such functionality, you need to add additional 
dependencies.
 
-=== Backup / Restore
-
-If an in-place upgrade is occurring, it's best to ensure that no Collection 
backups are being restored _while_ this happens.
-It's possible for a restored collection to not accept future indexing.
-
 === Deprecation removals
 
 * The `jaegertracer-configurator` module, which was deprecated in 9.2, is 
removed. Users should migrate to the `opentelemetry` module.
diff --git 
a/solr/solr-ref-guide/modules/upgrade-notes/pages/major-changes-in-solr-9.adoc 
b/solr/solr-ref-guide/modules/upgrade-notes/pages/major-changes-in-solr-9.adoc
index ec709ca2162..ecaf52fa859 100644
--- 
a/solr/solr-ref-guide/modules/upgrade-notes/pages/major-changes-in-solr-9.adoc
+++ 
b/solr/solr-ref-guide/modules/upgrade-notes/pages/major-changes-in-solr-9.adoc
@@ -46,6 +46,9 @@ If you are planning to upgrade your cluster using a rolling 
upgrade model (upgra
 
 Rolling upgrades from Solr 8 to Solr 9 require upgrading from Solr 8.7 or 
newer. If you run an 8.x. version prior to 8.7 we recommend that you first 
upgrade to 8.11.
 
+Certain commands, like a restore of a collection, might not complete properly 
if performed *during* an upgrade.
+They may need to be re-attempted after.
+
 *PKI Authentication*
 
 Internode communication secured by PKI Authentication has changed formats. For 
detailed information, see

Reply via email to