Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[OPTIONAL] Enable configuration of Apache Geode/PCC using both spring.data.gemfire.* and spring.data.geode.* properties. #8

Open
jxblum opened this issue Jun 1, 2018 · 0 comments

Comments

@jxblum
Copy link
Contributor

jxblum commented Jun 1, 2018

This new feature would add support for both spring.data.gemfire.* as well as spring.data.geode.* properties.

Of course, some sort of precedence is required if duplicate, but equivalent properties are configured, for example:

spring.data.gemfire.cache.log.level=INFO
...

spring-data-geode.cache.log.level=WARN

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.

@jxblum 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 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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant