You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For instance, should the log-level of the cache be WARN or INFO? 1 strategy could be that the last property definition wins. However, this can get quite confusing when the definitions are spread across multiple locations and property files, in addition to the use of Spring profiles.
The text was updated successfully, but these errors were encountered:
jxblum
changed the title
Enable parsing/configuration support for both spring.data.gemfire.* and spring.data.geode.* properties.
Enable configuration of Apache Geode/PCC using both spring.data.gemfire.* and spring.data.geode.* properties.
Jun 10, 2019
jxblum
changed the title
Enable configuration of Apache Geode/PCC using both spring.data.gemfire.* and spring.data.geode.* properties.
[OPTIONAL] Enable configuration of Apache Geode/PCC using both spring.data.gemfire.* and spring.data.geode.* properties.
Aug 5, 2023
This new feature would add support for both
spring.data.gemfire.*
as well asspring.data.geode.*
properties.Of course, some sort of precedence is required if duplicate, but equivalent properties are configured, for example:
For instance, should the log-level of the cache be WARN or INFO? 1 strategy could be that the last property definition wins. However, this can get quite confusing when the definitions are spread across multiple locations and property files, in addition to the use of Spring profiles.
The text was updated successfully, but these errors were encountered: