You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@lucene.apache.org by sh...@apache.org on 2018/01/23 03:41:02 UTC
lucene-solr:master: SOLR-11747: Fixed note in upgrade section
Repository: lucene-solr
Updated Branches:
refs/heads/master 183835ed2 -> e16da3570
SOLR-11747: Fixed note in upgrade section
Project: http://git-wip-us.apache.org/repos/asf/lucene-solr/repo
Commit: http://git-wip-us.apache.org/repos/asf/lucene-solr/commit/e16da357
Tree: http://git-wip-us.apache.org/repos/asf/lucene-solr/tree/e16da357
Diff: http://git-wip-us.apache.org/repos/asf/lucene-solr/diff/e16da357
Branch: refs/heads/master
Commit: e16da35707e5b48c063c08f2ef7bee13b4cb0cd0
Parents: 183835e
Author: Shalin Shekhar Mangar <sh...@apache.org>
Authored: Tue Jan 23 09:10:50 2018 +0530
Committer: Shalin Shekhar Mangar <sh...@apache.org>
Committed: Tue Jan 23 09:10:50 2018 +0530
----------------------------------------------------------------------
solr/CHANGES.txt | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/lucene-solr/blob/e16da357/solr/CHANGES.txt
----------------------------------------------------------------------
diff --git a/solr/CHANGES.txt b/solr/CHANGES.txt
index 0291a5f..1e612ad 100644
--- a/solr/CHANGES.txt
+++ b/solr/CHANGES.txt
@@ -64,8 +64,8 @@ Upgrade Notes
* SOLR-11747: The behaviour of the autoscaling system has been modified to pause all triggers from execution between
the start of actions and end of cool down period. The triggers will be resumed after the cool down period expires.
- Previously, the cool down period was a fixed period started after actions for a trigger event finish
- executing. During the cool down period, triggers wo
+ Previously, the cool down period was a fixed period started after actions for a trigger event complete and during
+ this time, all triggers continued to run but any events were rejected to be tried later.
* SOLR-11624: Collections created without specifying a configset name use a copy of the _default configset since 7.0.
Before 7.3, the copied over configset was named the same as the collection name, but 7.3 onwards it will be named