Add EnableClusterConfiguration annotation to push cluster configuration meta-data from the client to the server [DATAGEODE-34]

[spring-projects-issues]

John Blum opened DATAGEODE-34 and commented

This feature adds the @EnableClusterConfiguration annotation to the new Spring Data Geode Annotation based configuration model.

The feature and Annotation name (i.e. @EnableClusterConfiguration) should not be confused with Apache Geode's own Cluster Configuration Service, which records schema-like changes initiated from Gfsh or other JMX clients affecting the entire cluster and ensuring a consistent configuration when new nodes are brought online and added to the cluster.

However, this feature will have a similar effect. The schema changes introduced by using SD's Repository abstraction and specifically the mapping infrastructure with @EnableEntityDefinedRegions or Spring's Cache Abstraction with @EnableCachingDefinedRegions along with @EnableIndexing will determine the configuration cluster-side driven from a cache client application client-side (or technically, even a peer cache application)

---

No further details from DATAGEODE-34

[spring-projects-issues]

Oliver Drotbohm commented

I've removed this ticket from Kay RC3 as there didn't seem to be any commits yet and we need to issue the release today. Also, adding significant features during release candidate phase is generally discouraged

[spring-projects-issues]

John Blum commented

That is fine. However, this is going into Kay whether we like it or not. I too prefer to keep RC versions to bug fixes and minor enhancements as well. But, this is required by PCC. In addition, it has already been implemented; I am just working out the final bits on testing