Hi Kevin, I'm not sure I fully understand what you're trying to achieve. Can you describe your use case in more details? What is the purpose of this 'locking' field?
As for 'update_timestamp', I think you should not update it automatically on MySQL side, because cache will not know about this change. This is the same as if you make any update directly in database - you will need to trigger reload on cache side or use expirations. It's better to update the timestamp in cache value object before the update and persist it to the database from the store. Also note that you should not modify the object in store.write() method, because it's already serialized at this moment and the serialized form will not be changed. In case of timestamp you can utilize CacheInterceptor [1]. It's onBeforePut method will be called on the server node before updating the cache entry and the persistence store. [1] https://ignite.apache.org/releases/1.3.0/javadoc/index.html?org/apache/ignite/cache/CacheInterceptor.html -Val -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/CacheStore-implementation-using-Hibernate-tp1423p1451.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
