Skip to content

Integrated Redis Cache and Redis Sessions into Redis OM Spring. #608

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

foogaro
Copy link
Contributor

@foogaro foogaro commented Jun 19, 2025

Bringing Redis Cache and Redis Sessions into Redis OM Spring.

⚠️ Warnings
To keep a standard and "all-in-one" naming convention:

  • Redis Cache package has been renamed from com.redis.cache to com.redis.om.cache
  • Redis Sessions package has been renamed from com.redis.sessions to com.redis.om.sessions

@foogaro foogaro added enhancement New feature or request 1.2 labels Jun 19, 2025
@jeremyplichta
Copy link

👀

try {
jsonValues = connection.sync().jsonGet(key);
} catch (NullPointerException e) {
// Workaround for Lettuce 6.5 bug:

Choose a reason for hiding this comment

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

we shouldn't need this anymore rihgt since we are using Lettuce 6.7.1.RELEASE?

this.evictionLatency = Timer.builder("cache.evictions.latency").tag("name", name).description("Cache evictions")
.register(configuration.getMeterRegistry());
if (configuration.isIndexEnabled()) {
createIndex();

Choose a reason for hiding this comment

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

do we want to recreate the index every time RedisCache is instantiated? If this is running in multiple apps that come up and down in k8s pods for example it seems like it would be recreated a lot. Maybe check if its already created and in sync before dropping it?

throw new IllegalArgumentException(String.format("unparseable point %s", s));
}

return new GeoLoc(Double.parseDouble(parts[1]), Double.parseDouble(parts[1]));

Choose a reason for hiding this comment

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

is this a bug? Should it be parts[0] and parts[1]?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
1.2 enhancement New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants