[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-5260?page=c... ] Nikita Koksharov commented on HHH-5260: --------------------------------------- Because of this worked in jbosscache with hibernate 3.3.x. I migrated to infinispan in my application and noticed that cache configurations for different queries not loaded at all. For entities and collections all works right. We have base settings "entity" and "collections" and can customize it in hibernate.cfg.xml. For queries we should have the same functionality as been in hibernate-jbosscache module. For each query i can set the region as for entity and collections. And for one query there are should be and was (in hibernate-jbosscache) only one cache. There are no "both query caches". Where you get this? -- 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

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-5260?page=c... ] Galder Zamarreno commented on HHH-5260: --------------------------------------- Nikita, I'm still confused by your comments. WRT the following comment: " I migrated to infinispan in my application and noticed that cache configurations for different queries not loaded at all.". Could you show the hibernate.cfg.xml and jboss cache configuration file that you were using for this? I think there's misunderstanding going on here about regions and cache instances. Both JBossCache and Infinispan layers have always stored all queries under the same cache instance. The code change that you suggest results in queries for different regions being stored in different cache instances. What JBoss Cache used to do is use the region of a query to form the FQN under which the query was stored within the shared cache instance for all queries. In Infinispan, this region name is ignored and the query key is simply used as key in the cache itself. What I'm trying to understand is what is it that you're trying to gain out of having a different cache instance for each query region? Is it setting different eviction settings for each query region? The main advantage of using region names in the old JBoss Cache module is that you could then go to the jboss cache config file and set evictions for the specific FQN for the query region specified. To be able to do something similar with Infinispan yeah, we'd need to implement a change similar to what you suggest, where each query is stored under a cache instance with that region name. You'd then be able maxEntries, lifespan...etc and other type of eviction settings for that particular region. Again, please explain in more detail what is it that you're unable to do right now. -- 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

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-5260?page=c... ] Galder Zamarreno commented on HHH-5260: --------------------------------------- Nikita, I have other priorities at the moment, but if you're in a rush to have this done, do the following: - Implement the fix in either Hibernate core trunk or 3.5.x branch and make sure the Infinispan testsuite runs without failures. - Create a patch and attach it to the JIRA so that I can review it. - If approved, please sign the CLA in https://cla.jboss.org/login.seam?cid=1093 - Once that's done I'll apply the patch in trunk. -- 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

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-5260?page=c... ] Galder Zamarreno updated HHH-5260: ---------------------------------- Summary: Allow query region specific eviction settings (was: Allow query region specific eviction setttings) -- 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

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-5260?page=c... ] Galder Zamarreno commented on HHH-5260: --------------------------------------- Nikita, not sure if you ended up applying this code change somewhere in your environment, but your suggested fix is incomplete because you need to deal with the default region and get the appropiate default cache for it. See the Source tab for more info on the further changes I made. -- 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

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-5260?page=c... ] Galder Zamarreno commented on HHH-5260: --------------------------------------- I've updated documentation in: http://community.jboss.org/docs/DOC-14105 -- 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