Author: stevel
Date: Thu Apr  9 12:43:37 2015
New Revision: 1672321

URL: http://svn.apache.org/r1672321
Log:
SLIDER-600 role history enhancements

Modified:
    incubator/slider/site/trunk/content/design/rolehistory.md

Modified: incubator/slider/site/trunk/content/design/rolehistory.md
URL: 
http://svn.apache.org/viewvc/incubator/slider/site/trunk/content/design/rolehistory.md?rev=1672321&r1=1672320&r2=1672321&view=diff
==============================================================================
--- incubator/slider/site/trunk/content/design/rolehistory.md (original)
+++ incubator/slider/site/trunk/content/design/rolehistory.md Thu Apr  9 
12:43:37 2015
@@ -42,11 +42,11 @@ Role History Reloading Enhancements
 How persisted role history has also been improved 
[SLIDER-600]((https://issues.apache.org/jira/browse/SLIDER-600)
 
 1. Reloading of persistent history has been made resilient to changes in the 
number of roles.
-1. If there are more roles in the history than the current set, the surplus 
entries
+2. If there are more roles in the history than the current set, the surplus 
entries
 are discarded.
-1. If there are fewer, then the smaller set of roles are loaded
-1. The mapping of role name to role ID is persisted.
-1. There are tests to verify that the original role histories (those without 
maps) are reloaded.
+3. If there are fewer, then the smaller set of roles are loaded
+4. The mapping of role name to role ID is persisted.
+5. There are tests to verify that the original role histories (those without 
maps) are reloaded.
 
 There are no checks that the mapping of name to ID has not changed; the 
current model
 is "don't do that". If it is done while an application instance is stopped, 
the rebuilt


Reply via email to