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

Harmonize Redis key namespace configurations #1712

Merged
merged 1 commit into from
Nov 10, 2020

Conversation

vpavic
Copy link
Contributor

@vpavic vpavic commented Oct 2, 2020

At present, the RedisSessionRepository#setKeyNamespace expects users to provide the trailing colon (:) character that is used as separator between namespace segments. This is unlike RedisIndexedSessionRepository and ReactiveRedisSessionRepository that apply the separator implicitly in their respective #setRedisKeyNamespace methods.

This PR harmonizes the Redis key namespaces configurations across all Redis-backed session repository implementations.

I've noticed this while applying the approach from #1710 in one project.
Ideally, this should be merged before #1710 which should then updated to pick up the new #setRedisKeyNamespace method and use it in the sample.

At present, the RedisSessionRepository#setKeyNamespace expects users to provide the trailing colon (:) character that is used as separator between namespace segments. This is unlike RedisIndexedSessionRepository and ReactiveRedisSessionRepository that apply the separator implicitly in their respective #setRedisKeyNamespace methods.

This commit harmonizes the Redis key namespaces configurations across all Redis-backed session repository implementations.
@vpavic vpavic added type: bug A general bug in: redis labels Oct 2, 2020
@vpavic vpavic added this to the 2.4.0 milestone Oct 2, 2020
@eleftherias eleftherias modified the milestones: 2.4.0, 2.5.x Oct 12, 2020
@eleftherias
Copy link
Contributor

Thanks @vpavic!
I will merge this after the 2.4.0 release, in order to avoid API changes between RC1 and GA.

@vpavic
Copy link
Contributor Author

vpavic commented Oct 12, 2020

As labeled, this is IMO a bug and the change to address it is passive.

If you're that concerned about the API change (or an addition, to be more precise) I'd suggest to do an RC2 instead of postponing this for a full cycle.

@eleftherias eleftherias self-assigned this Nov 10, 2020
@eleftherias eleftherias modified the milestones: 2.5.x, 2.5.0-M1 Nov 10, 2020
@eleftherias eleftherias merged commit 55502f3 into spring-projects:master Nov 10, 2020
@vpavic vpavic deleted the harmonize-redis-config branch November 10, 2020 14:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants