Quarkus Redis Cache: expire-after-access config property

[AndreasPetersen]

Description

The Quarkus Cache with Caffeine as backend has the following property:

quarkus.cache.caffeine.expire-after-access

The Redis Cache backend, however, only has the following property:

quarkus.cache.redis.ttl

corrosponding to the Caffeine backend property:

quarkus.cache.caffeine.expire-after-write

Implementation ideas

A new property for the Redis backend similar to the one for the Caffeine backend:

quarkus.cache.caffeine.expire-after-access

[quarkus-bot]

/cc @cescoffier (redis), @gsmet (redis), @gwenneg (cache), @machi1990 (redis)

[cescoffier]

This can be implemented using the GETEX command.

[AndreasPetersen]

Thanks for the suggestion @cescoffier . The Quarkus Redis Cache guide does not seem to mention commands. The Redis Reference does however. Do I understand it correctly that we can use the Quarkus Cache with Redis as backend, in combination with the commands as described in the Redis reference?

[cescoffier]

That was more a note about how we could implement the feature (the backend implementation use the redis client underneath).

You can of course combine both, you just need to compute the keys.

[AndreasPetersen]

Amazing, thanks!