You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "Dan Smith (Jira)" <ji...@apache.org> on 2021/11/16 22:00:01 UTC
[jira] [Created] (GEODE-9813) Move geode-for-redis properties to the geode-for-redis module
Dan Smith created GEODE-9813:
--------------------------------
Summary: Move geode-for-redis properties to the geode-for-redis module
Key: GEODE-9813
URL: https://issues.apache.org/jira/browse/GEODE-9813
Project: Geode
Issue Type: Improvement
Reporter: Dan Smith
The goal is that geode-core should have no references to geode-for-redis gemfire properties.
This probably involves these steps:
* Change geode-core to support dynamically discovering modules that define new gemfire properties, perhaps using a service loader or other mechanism. Update the validation logic of gemfire properties to include these dynamically discovered properties.
* Move the definition of the geode-for-redis properties to the geode-for-redis module. This includes moving the public ConfigurationProperties constants to some new public interface in the geode-for-redis module.
We should consider deprecating and moving properties for other modules as well - for example the memcached properties.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)