From commits-return-106845-archive-asf-public=cust-asf.ponee.io@lucene.apache.org Mon Mar 4 16:28:53 2019 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx-eu-01.ponee.io (Postfix) with SMTP id 16780180627 for ; Mon, 4 Mar 2019 17:28:52 +0100 (CET) Received: (qmail 46853 invoked by uid 500); 4 Mar 2019 16:28:52 -0000 Mailing-List: contact commits-help@lucene.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@lucene.apache.org Delivered-To: mailing list commits@lucene.apache.org Received: (qmail 46844 invoked by uid 99); 4 Mar 2019 16:28:52 -0000 Received: from ec2-52-202-80-70.compute-1.amazonaws.com (HELO gitbox.apache.org) (52.202.80.70) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 04 Mar 2019 16:28:52 +0000 Received: by gitbox.apache.org (ASF Mail Server at gitbox.apache.org, from userid 33) id 7E0C48776A; Mon, 4 Mar 2019 16:28:51 +0000 (UTC) Date: Mon, 04 Mar 2019 16:28:51 +0000 To: "commits@lucene.apache.org" Subject: [lucene-solr] branch jira/solr-13259 updated: SOLR-13259: clarify a bit from feedback; add DELETE collection example MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Message-ID: <155171693139.32510.17699776457908373623@gitbox.apache.org> From: ctargett@apache.org X-Git-Host: gitbox.apache.org X-Git-Repo: lucene-solr X-Git-Refname: refs/heads/jira/solr-13259 X-Git-Reftype: branch X-Git-Oldrev: a2223d0bf27865efcaeedc7c058661f6c46ff883 X-Git-Newrev: e3d46972738033647e23779ff730038847947b81 X-Git-Rev: e3d46972738033647e23779ff730038847947b81 X-Git-NotificationType: ref_changed_plus_diff X-Git-Multimail-Version: 1.5.dev Auto-Submitted: auto-generated This is an automated email from the ASF dual-hosted git repository. ctargett pushed a commit to branch jira/solr-13259 in repository https://gitbox.apache.org/repos/asf/lucene-solr.git The following commit(s) were added to refs/heads/jira/solr-13259 by this push: new e3d4697 SOLR-13259: clarify a bit from feedback; add DELETE collection example e3d4697 is described below commit e3d46972738033647e23779ff730038847947b81 Author: Cassandra Targett AuthorDate: Mon Mar 4 10:28:13 2019 -0600 SOLR-13259: clarify a bit from feedback; add DELETE collection example --- solr/solr-ref-guide/src/reindexing.adoc | 14 ++++++++++---- 1 file changed, 10 insertions(+), 4 deletions(-) diff --git a/solr/solr-ref-guide/src/reindexing.adoc b/solr/solr-ref-guide/src/reindexing.adoc index ec90ef0..efd7573 100644 --- a/solr/solr-ref-guide/src/reindexing.adoc +++ b/solr/solr-ref-guide/src/reindexing.adoc @@ -102,7 +102,7 @@ If you change the analysis chain that applies to indexing events, it is strongly This is because all of the changes that occur due to the chain configuration are applied to documents as they are being indexed, and only reindexing will allow your changes to take effect on documents. -While not reindexing after analyzer changes is not required, be aware that not reindexing can cause unexpected +While reindexing after analyzer changes is not required, be aware that not reindexing can cause unexpected query results in many cases. For example, if you indexed a number of documents and then decide you'd like to use the `LowerCaseTokenizerFactory` @@ -132,8 +132,9 @@ The reason for this is that subtle changes may occur in default field type defin [NOTE] If you have *not* changed your schema as part of an upgrade from one minor release to another (such as, from 7.x -to 7.x), you can often get away with reindexing your documents without first deleting your index. However, when -upgrading to a major release, you should plan to reindex your documents because of the likelihood of changes that break back-compatibility. +to a later 7.x release), you can often skip reindexing your documents. +However, when upgrading to a major release, you should plan to reindex your documents because of the likelihood of +changes that break back-compatibility. == Reindexing Strategies @@ -174,7 +175,12 @@ to the new collection seamlessly. Here is an example of creating an alias that points to a single collection: [source,bash] -http://localhost:8983/solr/admin/collections?action=CREATEALIAS&name=myData&collections=oldCollection +http://localhost:8983/solr/admin/collections?action=CREATEALIAS&name=myData&collections=newCollection + +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 <> of the Collections API: + +[source,bash] +http://localhost:8983/solr/admin/collections?action=DELETE&name=oldCollection == Changes that Do Not Require Reindex