DATAREDIS-574 - Introduce dedicated RedisClientConfig #236
Add this suggestion to a batch that can be applied as a single commit. This suggestion is invalid because no changes were made to the code. Suggestions cannot be applied while the pull request is closed. Suggestions cannot be applied while viewing a subset of changes. Only one suggestion per line can be applied in a batch. Add this suggestion to a batch that can be applied as a single commit. Applying suggestions on deleted lines is not supported. You must change the existing code in this line in order to create a valid suggestion. Outdated suggestions cannot be applied. This suggestion has been applied or marked resolved. Suggestions cannot be applied from pending reviews. Suggestions cannot be applied on multi-line comments. Suggestions cannot be applied while the pull request is queued to merge. Suggestion cannot be applied right now. Please check back later.
Add
JedisClientConfiguration
andLettuceClientConfiguration
to abstract client-specific features with their configuration options. Client configurations are built with a builder that create immutable instances. Client configurations replace property storage within aRedisConnectionFactory
. ARedisConnectionFactory
created without a client configuration uses a mutable client configuration.Lettuce:
Jedis:
Add
RedisStandaloneConfiguration
to be consistent withRedisSentinelConfiguration
andRedisClusterConfiguration
and extend environmental configuration with password and database (Standalone and Sentinel).Remove system properties defined for surefire because they are not used and
javax.net.ssl.keyStore
causes exceptions when obtaining the default SSL context.Related ticket: DATAREDIS-574.