This is an automated email from the ASF dual-hosted git repository.
noble pushed a commit to branch branch_9x
in repository https://gitbox.apache.org/repos/asf/solr.git
The following commit(s) were added to refs/heads/branch_9x by this push:
new d7c9fbf2db7 Update reindexing.adoc (#1228)
d7c9fbf2db7 is described below
commit d7c9fbf2db75a401eeb7a88187ae0283bca89850
Author: Arvind-Avinash <[email protected]>
AuthorDate: Tue Dec 20 07:28:47 2022 +0000
Update reindexing.adoc (#1228)
---
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 85b2bddfd08..cdf56150b24 100644
--- a/solr/solr-ref-guide/modules/indexing-guide/pages/reindexing.adoc
+++ b/solr/solr-ref-guide/modules/indexing-guide/pages/reindexing.adoc
@@ -41,7 +41,7 @@ This is because many of the available options are only
applied during the indexi
Solr has no way to implement the desired change without reindexing the data.
To understand the general reason why reindexing is ever required, it's helpful
to understand the relationship between Solr's schema and the underlying Lucene
index.
-Lucene does not use a schema, schemas are a Solr-only concept.
+Lucene does not use a schema, schema is a Solr-only concept.
When you change Solr's schema, the Lucene index is not modified in any way.
This means that there are many types of schema changes that cannot be
reflected in the index simply by modifying Solr's schema.
