We had a discussion about this and decided it would be better to remove this 
restriction on the update. The failure to update prRoot resulting in validation 
failures is no intended behavior and we don't believe we have customers relying 
on that behavior, so it's better to have the fix work for all Geode 
configuration methods and not just cluster configuration.

[ Full content available at: https://github.com/apache/geode/pull/3308 ]
This message was relayed via gitbox.apache.org for 
[email protected]

Reply via email to