[lucene-solr] branch branch_8_4 updated: SOLR-14071: Updating upgrade notice

[is...@apache.org]

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

ishan pushed a commit to branch branch_8_4
in repository https://gitbox.apache.org/repos/asf/lucene-solr.git


The following commit(s) were added to refs/heads/branch_8_4 by this push:
     new b62b189  SOLR-14071: Updating upgrade notice
b62b189 is described below

commit b62b1898060d1dd895cb3101e004e752eb5d7229
Author: Ishan Chattopadhyaya <is...@apache.org>
AuthorDate: Sun Dec 15 11:21:10 2019 +0530

    SOLR-14071: Updating upgrade notice
---
 solr/CHANGES.txt | 7 +++++--
 1 file changed, 5 insertions(+), 2 deletions(-)

diff --git a/solr/CHANGES.txt b/solr/CHANGES.txt
index f636f28..db7ae08 100644
--- a/solr/CHANGES.txt
+++ b/solr/CHANGES.txt
@@ -64,6 +64,9 @@ Upgrade Notes
 
 * SOLR-14071: Untrusted configsets (ones that are uploaded via unsecured configset API) cannot use <lib> directive.
   Consider enabling authentication/authorization so that the uploaded configsets are trusted.
+  Note: If you already have a collection using untrusted configset that uses <lib> directive, it will not load after
+  upgrading to 8.4. You can re-upload your configset using "bin/solr zk -upconfig .." or place your libraries in the
+  classpath and restart Solr.
 
 * SOLR-14065: VelocityResponseWriter has been deprecated and may be removed in a future version.
 
@@ -198,9 +201,9 @@ Bug Fixes
 * SOLR-13945: Fix: SPLITSHARD can cause data loss on a failure to commit after the sub-shards are active and a rollback
   is done to make parent shard active again (Ishan Chattopadhyaya, ab)
 
-* SOLR-14013: FIX: javabin performance regressions (noble, yonik, Houston Putman)
+* SOLR-14071: Untrusted configsets cannot use <lib> directive due to security reasons (Ishan Chattopadhyaya)
 
-* SOLR-14071: Untrusted configsets cannot use <lib> directive (Ishan Chattopadhyaya)
+* SOLR-14013: FIX: javabin performance regressions (noble, yonik, Houston Putman)
 
 * SOLR-14079: SPLITSHARD splitByPrefix doesn't work in async mode.  This also
   affects splits triggered by the autoscale framework, which use async mode.