[infinispan-issues] [JBoss JIRA] Updated: (ISPN-717) Trying to modify an entry that is not loaded into memory triggers an unnecessary CacheStore.load() operation.

[ https://jira.jboss.org/browse/ISPN-717?page=com.atlassian.jira.plugin.sys... ] Trustin Lee updated ISPN-717: ----------------------------- Summary: Trying to modify an entry that is not loaded into memory triggers an unnecessary CacheStore.load() operation. (was: Implement a SKIP_CACHE_LOAD flag to prevent loading an entry) Issue Type: Bug (was: Feature Request) Fix Version/s: 5.0.0.BETA1 (was: 4.2.0.BETA1) (was: 4.2.0.Final) Affects Version/s: 4.2.0.Final (was: 4.2.0.ALPHA3) (was: 4.2.0.ALPHA2) (was: 4.2.0.ALPHA1) Description: There is no reason to load an entry from CacheStore to memory before modifying it. The current implementation triggers CacheStore.load() unnecessarily when a user calls Cache.put(). (was: This will allow for the suppression of loading an entry from a cache loader if the return value from a call such as Cache.put() it is deemed unnecessary by the caller and would not be used. Analogous to the SKIP_REMOTE_LOOKUP flag for remote retrieval of entries for the sake of return values. http://docs.jboss.org/infinispan/4.2/apidocs/org/infinispan/context/Flag....) Complexity: (was: Low) Component/s: (was: Loaders and Stores) Currently, CacheStore.store(), which is directly associated with Cache.put() returns void. It could be changed to return a previous value, then there is no need for put() to call CacheStore.load() just to get the previous value. This breaks API backward compatibility for those who implemented their custom CacheStore, so it should be done in 5.0. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira