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

Upgrade Spring boot to 2.0.2.RELEASE and spring security to 2.3.3.RELEASE #8

Open
wants to merge 6 commits into
base: master
Choose a base branch
from

Conversation

danapsimer
Copy link

Upgrading to the latest spring boot and latest spring security brings with it significant changes to spring-data-cassandra. This PR represents changes to keep the implementation largely the same while accommodating the changes in API.

@@ -24,4 +24,6 @@ build/
nbbuild/
dist/
nbdist/
.nb-gradle/
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

newline please.

Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This will be automatically fixed for you when you do a git pull.

@@ -0,0 +1 @@
rootProject.name = 'spring-oauth2-cassandra-token-store'
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

newline please

@@ -28,7 +28,7 @@

@Override
public SchemaAction getSchemaAction() {
return SchemaAction.CREATE_IF_NOT_EXISTS;
return SchemaAction.RECREATE;
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This can be problematic for a rolling upgrade. Shouldn't we keep the existing tokens in the DB since we are not altering DB schema?

Copy link
Owner

@Mert-Z Mert-Z left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nice wrap up 👍

@Mert-Z Mert-Z mentioned this pull request Sep 27, 2018
@Mert-Z
Copy link
Owner

Mert-Z commented Sep 27, 2018

Just a side note; it would also be nice to use new Cassandra 3.x materialised views instead of data duplication. That will avoid so many inserts on multiple tables and decrease the risk of having stale/unsync data between tables. On the other hand this will require migration of existing data to the new schema which can be costly. Can be done in a future story may be. :)


version = '0.0.1-SNAPSHOT'
group = 'mertz.security'
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

group = 'com.github.mert-z'
This will be automatically fixed for you when you do a git pull.

@Mert-Z
Copy link
Owner

Mert-Z commented Oct 25, 2018 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants