Cache TTL (Time To Live) property required. [DATACOUCH-25] about spring-data-couchbase HOT 5 CLOSED

Michael Nitschinger commented

Hi Krishna,

I looked over the code from hazelcast and also didn't see the cache TTL exposed - can you give me an example on how they do that? As far as I know, the spring cache API doesn't expose the TTL explicitly but I would really like to support that.

Let me know and we'll make that happen

from spring-data-couchbase.

Michael Nitschinger commented

What we could do easily is to expose it on the CacheManager, since you can configure that directly. What will be harder is to do it on a per-key basis, maybe we can do that with a annotation on the method, but this needs more thought.

What is your use case here? instance wide TTL or on a per-key basis?

from spring-data-couchbase.

Michael Nitschinger commented

I'm afraid this can't be done easily with the current implementation. The spring docs state explicitly that its not the focus of this API..

If you need it please use the CouchbaseClient API directly. For related needs, the @CacheEvict annotation can help!

Also see http://docs.spring.io/spring/docs/3.2.4.RELEASE/spring-framework-reference/html/cache.html#cache-specific-config

from spring-data-couchbase.

Konrad Król commented

Hey, I think it doesn't make sense to provide cache abstraction where you can't say how long you want to cache objects. That's why I did my fork and pull request that covers functionality requested in this bug. Please take a look here:
#36

from spring-data-couchbase.

Michael Nitschinger commented

I've merged your changes Konrad, thanks much!

Btw, we are working on a Jcache adapter for the 2.0 sdk, so this one can in the future also be used with spring

from spring-data-couchbase.