Invalid @Cachable annotation entries on an interface?

Question

I am using spring annotation and @Cacheable to cache some records in the database. I want to disable the full cache periodically.

Therefore: is it really easy to put these annotations on an interface method? Or should these annotations be placed in class methods (even if they have an empty piece of the method)?

 public interface MyRepository extends CrudRepository<MyEntity, Long> { @Override @Cacheable("cache") Airline findOne(long id); @CacheEvict(value = "cache", allEntries = true) @Scheduled(cron = "0 0 1 * * *") void removeAll(); } 

The application starts successfully if I have the @Cacheable interface method and @CacheEvict in the service. This does not work if I use the code above. But maybe I'm doing it wrong too?

Answer 1

Maybe this will work, but I would suggest posting these annotations for implementation.

This is more of a theoretical question, but think of it this way: the interface is a common contract, but caching is an implementation detail .

Your interface can be implemented in several ways, for example, one day you can have an HsqlDBRepository, for which caching does not make sense at all, since it is already in memory.

On the side of the note, I would carefully think about why you need to “evict everyone” ... depending on how often this happens, this can make your caching useless - it is also often a sign of a deeper design problem. If you want to evict objects after a while, consider setting up timeToLive / timeToIdle - most cache backends support this beautifully.