The main reason we added this stipulation is so we don't disrupt any clients who have workflows set up around defining the region with the original definition and re-mutating the region on each new member. That workflow would already be disrupted if the user were to use cluster config, as cluster config would attempt to define the region based on it's cluster configuration definition after the loader/writer was added.
If we don't think that would be an issue for users, then we could definitely remove it. [ Full content available at: https://github.com/apache/geode/pull/3308 ] This message was relayed via gitbox.apache.org for [email protected]
