spring-projects / spring-projects/spring-session
How to upgrade Spring Session JDBC from 1.5.x to 2.1.x
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.9k
- Forks
- 1.2k
- Avg merge
- 4h 27m
- Merged PRs (30d)
- 55
Description
I noticed that the newer versions of spring session support changing of the session id.
Additionally, the spring-session-jdbc scripts now have backwards-incompatible changes.
spring_session table - session_primary_id is now the PK
spring_session_attributes table - session_primary_id is now the FK to spring_session
If we want to upgrade, we would essentially need to drop the tables or run the appropriate alter statements. If we have multiple services, is there any suggested backwards compatible way to go about upgrading without having to stop and re-deploy them all at the same time?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the Spring Session JDBC upgrade guidance and the spring_session and spring_session_attributes schema changes described in the issue. Document a migration path for multiple services that avoids requiring all services to stop and redeploy simultaneously, including what compatibility and completion look like.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring
- Domain
- database
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100