]
Keith Mashinter commented on HHH-4055:
--------------------------------------
I vote for this as well. I'm working on a NamedScalarQueryCache that works more like
HTTP URL caches where it works by timeout or forced invalidation but doesn't evict by
any-row-change. This is more for the case where we want to select a summary of
information and don't care if it changes second-to-second but would rather cache the
results for at least a few minutes if not more.
make UpdateTimestampsCache pluggable, like QueryCache
-----------------------------------------------------
Key: HHH-4055
URL:
http://opensource.atlassian.com/projects/hibernate/browse/HHH-4055
Project: Hibernate Core
Issue Type: Improvement
Components: caching (L2)
Affects Versions: 3.3.2
Environment: all
Reporter: A. R.
According to
https://www.hibernate.org/213.html, one can plug-in one's own query
cache using hibernate.cache.query_cache_factory, e.g. to chose a cache strategy that is
not based on updateTimestamps.
However, Hibernate's SessionFactoryImpl will always create an UpdateTimestampsCache
if the Query Cache is enabled, even for custom Query Caches. This UpdateTimestampsCache
then is always used in org.hibernate.engine.ActionQueue.execute() and
afterTransactionCompletion(). Since the UpdateTimestampsCache is synchronized, this can
cause bottlenecks when many threads change things (see
http://tech.puredanger.com/2009/07/10/hibernate-query-cache/)..
Please make the UpdateTimestampsCache also pluggable, so that one can truly and
completely plug one's own Query Cache without using a Update-Timestamps or with a
custom UpdateTimestampCache.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: