[hibernate-issues] [Hibernate-JIRA] Commented: (HHH-5260) Tweak for query-cache via hibernate.hbm.xml needed
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-5260?page=c...
]
Galder Zamarreno commented on HHH-5260:
---------------------------------------
Niktia, why is that you want this? Why do you consider current functionality in this area
incorrect?
Regardless, I'm not sure this is really feasible. If you have a query that expands
multiple entities, in which query cache do you store it and based on which rules? If you
store in both query caches for both entity types, that's waste of space.
Tweak for query-cache via hibernate.hbm.xml needed
--------------------------------------------------
Key: HHH-5260
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5260
Project: Hibernate Core
Issue Type: New Feature
Components: caching (L2)
Reporter: Galder Zamarreno
Assignee: Galder Zamarreno
From Niktia Koksharov in https://jira.jboss.org/browse/ISPN-458:
"In current implementation of hibernate-infinispan we can tune only entity and
collection settings via hibernate.xml.cfg. But tuning in same way for queries needed too.
In current version there are always the same cache region for all queries (look at
org.hibernate.cache.infinispan.InfinispanRegionFactory.buildQueryResultsRegion) and
it's incorrect.
In org.hibernate.cache.infinispan.InfinispanRegionFactory.buildQueryResultsRegion
Replace those lines:
String cacheName = typeOverrides.get(QUERY_KEY).getCacheName();
CacheAdapter cacheAdapter =
CacheAdapterImpl.newInstance(manager.getCache(cacheName));
To:
Cache cache = getCache(regionName, QUERY_KEY, properties);
CacheAdapter cacheAdapter = CacheAdapterImpl.newInstance(cache); "
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see: http://www.atlassian.com/software/jira