You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@solr.apache.org by ep...@apache.org on 2022/08/22 19:15:22 UTC

[solr] branch main updated: Mention REINDEXCOLLECTION in Reindexing docs (#974)

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

epugh 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 9654879e90f Mention REINDEXCOLLECTION in Reindexing docs (#974)
9654879e90f is described below

commit 9654879e90fa79a056247ad9b7e880c2493bf92e
Author: Radu Gheorghe <ra...@sematext.com>
AuthorDate: Mon Aug 22 22:15:16 2022 +0300

    Mention REINDEXCOLLECTION in Reindexing docs (#974)
    
    Added a mention of it under the Index to Another Collection strategy.
---
 solr/solr-ref-guide/modules/indexing-guide/pages/reindexing.adoc | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/solr/solr-ref-guide/modules/indexing-guide/pages/reindexing.adoc b/solr/solr-ref-guide/modules/indexing-guide/pages/reindexing.adoc
index 7b0bf113ad3..5963550b5f0 100644
--- a/solr/solr-ref-guide/modules/indexing-guide/pages/reindexing.adoc
+++ b/solr/solr-ref-guide/modules/indexing-guide/pages/reindexing.adoc
@@ -156,7 +156,7 @@ Another approach is to use index to a new collection and use Solr's xref:deploym
 
 This option is only available for Solr installations running in SolrCloud mode.
 
-With this approach, you will index your documents into a new collection that uses your changes and, once indexing and testing are complete, create an alias that points your front-end at the new collection.
+With this approach, you will index your documents into a new collection that uses your changes. If you store all the fields, you can use the xref:deployment-guide:collection-management.adoc#reindexcollection[REINDEXCOLLECTION command] to reindex from the old collection to the new one. Once indexing and testing are complete, create an alias that points your front-end at the new collection.
 From that point, new queries and updates will be routed to the new collection seamlessly.
 
 Once the alias is in place and you are satisfied you no longer need the old data, you can delete the old collection with the Collections API xref:deployment-guide:collection-management.adoc#delete[DELETE command].