ErickErickson commented on a change in pull request #2009:
URL: https://github.com/apache/lucene-solr/pull/2009#discussion_r508899237
##########
File path: solr/solr-ref-guide/src/reindexing.adoc
##########
@@ -21,148 +21,95 @@ There are several types of changes to Solr configuration
that require you to rei
These changes include editing properties of fields or field types; adding
fields, field types, or copy field rules;
upgrading Solr; and some system configuration properties.
-It's important to be aware that many changes require reindexing, because there
are times when not reindexing
-can have negative consequences for Solr as a system, or for the ability of
your users to find what they are looking for.
+It's important to be aware that many changes require reindexing, because
failing to reindex can have both obvious and subtle consequences for Solr or
for the ability of your users to find what they are looking for.
-There is no process in Solr for programmatically reindexing data. When we say
"reindex", we mean, literally,
-"index it again". However you got the data into the index the first time, you
will run that process again.
-It is strongly recommended that Solr users index their data in a repeatable,
consistent way, so that the process can be
-easily repeated when the need for reindexing arises.
+"Reindex" in this context means _first delete the existing index and repeat
the process you used to ingest the entire corpus from the system-of-record_. It
is strongly recommended that Solr users index their data in a repeatable,
consistent way, so that the process can be easily repeated when the need for
reindexing arises.
+
+[CAUTION]
+====
+Re-ingesting all the documents in your corpus without first insuring that all
documents and Lucene segments have been deleted is *not* sufficient, see the
section below <<reindexing.adoc#reindexing-strategies,Reindexing Strategies>>.
Review comment:
They're interchangeable.
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
