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?
to your account
abccbaandy opened DATAREDIS-714 and commented
HashOperations<String, String, String> hashOperations = redisTemplate.opsForHash();
Map<String, String> map = hashOperations.entries("2330");
redis monitor :
it should be only this, isn't it?
I submit this issue to spring boot few days before, but maybe here is better place to submit this issue?
Affects: 1.8.7 (Ingalls SR7)
DATAREDIS-244 Select db index maybe cause resource wasted when user only use one db index larger than 0
DATAREDIS-10 JedisConnection may fail to select database
DATAREDIS-790 Backport JedisConnection always executes SELECT via RedisTemplate
Referenced from: pull request #291
Backported to: 2.0.3 (Kay SR3)
The text was updated successfully, but these errors were encountered:
Mark Paluch commented
Please do not cross-post. In any case, this is the appropriate issue tracker for Spring Data Redis
Sorry, something went wrong.
It seems the code originates from a Jedis version where database selection and pooling did not reliably work. I think we can simplify things here
It would make sense to back-port this improvement to Ingalls and Kay. WDYT?
This feature is on spring-data-redis 2.0 now, can you merge it into elder versions like 1.8?
Because spring-data-redis 2.0 will bring in spring framework 5.0, and you know, upgrading framework is much harder than upgrading spring-data:P
kyleyu I filed DATAREDIS-790 to backport the change to the upcoming 1.8.11 release
thank you for your patient replies(y)
No branches or pull requests