You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@lucene.apache.org by ct...@apache.org on 2019/03/29 20:45:57 UTC
svn commit: r1856578 - /lucene/cms/trunk/content/solr/news.mdtext
Author: ctargett
Date: Fri Mar 29 20:45:57 2019
New Revision: 1856578
URL: http://svn.apache.org/viewvc?rev=1856578&view=rev
Log:
Fix versions referenced for 7.7.1 bug - 7.6 not 7.5
Modified:
lucene/cms/trunk/content/solr/news.mdtext
Modified: lucene/cms/trunk/content/solr/news.mdtext
URL: http://svn.apache.org/viewvc/lucene/cms/trunk/content/solr/news.mdtext?rev=1856578&r1=1856577&r2=1856578&view=diff
==============================================================================
--- lucene/cms/trunk/content/solr/news.mdtext (original)
+++ lucene/cms/trunk/content/solr/news.mdtext Fri Mar 29 20:45:57 2019
@@ -62,11 +62,11 @@ Please read CHANGES.txt for a full list
* Bugfix for ClassCastException when URPs try to read a String field which returns a ByteArrayUTF8CHarSequence (a
regression in release 7.7.0).
- * Bugfix: Autoscaling based replica placement was broken out of the box. Solr 7.5 enabled autoscaling based replica
+ * Bugfix: Autoscaling based replica placement was broken out of the box. Solr 7.6 enabled autoscaling based replica
placement by default but in the absence of default cluster policies, autoscaling can place more than 1 replica of the
same shard on the same node. Also, the maxShardsPerNode and createNodeSet was not respected. Due to these reasons,
this issue reverts the default replica placement policy to the 'legacy' assignment policy that was the default until
- Solr 7.4.
+ Solr 7.5.
## 11 February 2019, Apache Solr⢠7.7.0 available