Hi Czeslaw, Please properly subscribe to the mailing list so that the community can receive email notifications for your messages. To subscribe, send empty email to [email protected] and follow simple instructions in the reply.
cszczotka wrote > I’m using cache with read-through/write-through configuration and with > database persistent store handled by hibernate Dao –s. Hibernate Dao –s ( > it is legacy code) also handling versioning and optimistic locking. > So situation looks like when I put into cache some entity this entity is > written to database with version 1 set by hibernate but in cache I have > entity with version 0. Calling get method on cache doesn’t help because > this entity is in cache and load method from persistance store is not > called. > Do you have good way how to force ignite to refresh cache from DB ? I see > in ignite documentation that I can subscribe on event > EventType.EVT_CACHE_OBJECT_PUT and programmatically call load method on > cache. Do you see better way ? I think it's better to configure CacheInterceptor and implement reload logic in onAfterPut method. However, this will be a performance overhead. -Val -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Cache-refresh-because-of-hibernate-versioning-mechanism-tp14394p14435.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
