[Hibernate-JIRA] Erstellt: (HHH-2224) executeUpdate causes coarse cache invalidation

[Hibernate-JIRA] Commented:...

[Hibernate-JIRA] Created:...

Stefan Fleiter (JIRA)

Thursday, 9 November 2006 Thu, 9 Nov '06

7:32 a.m.

executeUpdate causes coarse cache invalidation ---------------------------------------------- Key: HHH-2224 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2224 Project: Hibernate3 Type: Improvement Versions: 3.2.0.ga Environment: Hibernate 3.2.0.ga, Oracle 9.2 Reporter: Stefan Fleiter Attachments: bulk_testcase.zip I am developing an application and want to mix bulk-updates with normal hibernate operations. The bulk updates work fine, but invalidate the whole region and I've found no possibility to prevent this. There would be 3 options to improve: - Invalidate only the modified objects if the ids where given as Query-parameters. - Let me deactivate the invalidation so I can invalidate the affected objects myself. - Transform the DML to a select to gather the objects to invalidate before executing the DML The reference documentation does not mention caching at all: http://www.hibernate.org/hib_docs/v3/reference/en/html_single/#batch-direct The best documentation I've found is: http://blog.hibernate.org/cgi-bin/blosxom.cgi/2005/07/19#dml-basic Maybe this could be added to the reference documentation... I already posted this at the forum http://forum.hibernate.org/viewtopic.php?t=966775 but did not get a single answer. I've attached a testcase for 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

Show replies by date

Karl Smola (JIRA)

Wednesday, 13 August Wed, 13 Aug

3:42 a.m.

New subject: [Hibernate-JIRA] Commented: (HHH-2224) executeUpdate causes coarse cache invalidation

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-2224?page=c... ] Karl Smola commented on HHH-2224: --------------------------------- Hi Stephan, I have been experience exactly the same issues, details of my test case and my observations are available in this post: http://forum.hibernate.org/viewtopic.php?t=989568. I noticed that this issue has been logged as an improvement, has the hibernate team confirmed this is the intended behavior? I find it hard to believe that any application that uses 2nd level caching is unable to use DML or SQL style bulk updates without clearing the cache. If it is the intended behavior then this bug need to be filed under documentation as I found no references to bulk updates or second level caching. Regards Karl Smolka

...

executeUpdate causes coarse cache invalidation ---------------------------------------------- Key: HHH-2224 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2224 Project: Hibernate3 Issue Type: Improvement Affects Versions: 3.2.0.ga Environment: Hibernate 3.2.0.ga, Oracle 9.2 Reporter: Stefan Fleiter Attachments: bulk_testcase.zip I am developing an application and want to mix bulk-updates with normal hibernate operations. The bulk updates work fine, but invalidate the whole region and I've found no possibility to prevent this. There would be 3 options to improve: - Invalidate only the modified objects if the ids where given as Query-parameters. - Let me deactivate the invalidation so I can invalidate the affected objects myself. - Transform the DML to a select to gather the objects to invalidate before executing the DML The reference documentation does not mention caching at all: http://www.hibernate.org/hib_docs/v3/reference/en/html_single/#batch-direct The best documentation I've found is: http://blog.hibernate.org/cgi-bin/blosxom.cgi/2005/07/19#dml-basic Maybe this could be added to the reference documentation... I already posted this at the forum http://forum.hibernate.org/viewtopic.php?t=966775 but did not get a single answer. I've attached a testcase for 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

Patrick Kranz (JIRA)

Wednesday, 25 March Wed, 25 Mar

11:12 a.m.

New subject: [Hibernate-JIRA] Commented: (HHH-2224) executeUpdate causes coarse cache invalidation

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-2224?page=c... ] Patrick Kranz commented on HHH-2224: ------------------------------------ Hi you two, I don´t really understand what the problem is you guys are experiencing. The blog entry you mentioned (http://blog.hibernate.org/cgi-bin/blosxom.cgi/2005/07/19#dml-basic) explains why Hibernate behaves like it does. Basically it is because if you execute an update on the database Hibernate has no way of knowing which objects are obsolete. So, it invalidates the whole cache region. The other option would be to reload all the objects in the cache but this will happen anyway if you ask for those objects again since the regions is invalidated. So in my opinion, the behavior as is, is the preferred one. Regarding your three options: - If you know the ids of the objects you want to modify, you don´t need a bulk update operation. You can retrieve the objects from the 2nd level cache and manipulate them directly. Since they are in your cache no DB round trip is needed. The changes are in your cache and all is fine. - If you start invalidating the objects yourself you will forget it somewhere, trust me, and you will end up with hard to find bugs or stale data but it will definitely be worse than the "performance loss" of another DB round trip. - again, in this case, why not load the objects yourself and do the modification. seems like you are loosing yourself in the old "for someone with a hammer, every problem looks like a nail"-paradigm ;-) Best regards, Patrick

...

executeUpdate causes coarse cache invalidation ---------------------------------------------- Key: HHH-2224 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2224 Project: Hibernate Core Issue Type: Improvement Affects Versions: 3.2.0.ga Environment: Hibernate 3.2.0.ga, Oracle 9.2 Reporter: Stefan Fleiter Attachments: bulk_testcase.zip I am developing an application and want to mix bulk-updates with normal hibernate operations. The bulk updates work fine, but invalidate the whole region and I've found no possibility to prevent this. There would be 3 options to improve: - Invalidate only the modified objects if the ids where given as Query-parameters. - Let me deactivate the invalidation so I can invalidate the affected objects myself. - Transform the DML to a select to gather the objects to invalidate before executing the DML The reference documentation does not mention caching at all: http://www.hibernate.org/hib_docs/v3/reference/en/html_single/#batch-direct The best documentation I've found is: http://blog.hibernate.org/cgi-bin/blosxom.cgi/2005/07/19#dml-basic Maybe this could be added to the reference documentation... I already posted this at the forum http://forum.hibernate.org/viewtopic.php?t=966775 but did not get a single answer. I've attached a testcase for this.

Karl Smola (JIRA)

2 p.m.

New subject: [Hibernate-JIRA] Commented: (HHH-2224) executeUpdate causes coarse cache invalidation

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-2224?page=c... ] Karl Smola commented on HHH-2224: --------------------------------- Evening Patrick, Due to the lack of official documentation on the matter I though it would be good to get an official word on the subject as I did find it odd that Hibernate "has no way of knowing which objects are obsolete" but I guess it does make sense, please feel free to refile as a documentation bug. Karl

...

executeUpdate causes coarse cache invalidation ---------------------------------------------- Key: HHH-2224 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2224 Project: Hibernate Core Issue Type: Improvement Affects Versions: 3.2.0.ga Environment: Hibernate 3.2.0.ga, Oracle 9.2 Reporter: Stefan Fleiter Attachments: bulk_testcase.zip I am developing an application and want to mix bulk-updates with normal hibernate operations. The bulk updates work fine, but invalidate the whole region and I've found no possibility to prevent this. There would be 3 options to improve: - Invalidate only the modified objects if the ids where given as Query-parameters. - Let me deactivate the invalidation so I can invalidate the affected objects myself. - Transform the DML to a select to gather the objects to invalidate before executing the DML The reference documentation does not mention caching at all: http://www.hibernate.org/hib_docs/v3/reference/en/html_single/#batch-direct The best documentation I've found is: http://blog.hibernate.org/cgi-bin/blosxom.cgi/2005/07/19#dml-basic Maybe this could be added to the reference documentation... I already posted this at the forum http://forum.hibernate.org/viewtopic.php?t=966775 but did not get a single answer. I've attached a testcase for this.

Vladimir Kralik (JIRA)

Friday, 15 May Fri, 15 May

10:11 a.m.

New subject: [Hibernate-JIRA] Commented: (HHH-2224) executeUpdate causes coarse cache invalidation

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-2224?page=c... ] Vladimir Kralik commented on HHH-2224: -------------------------------------- Hi all, I've similar problem, i need use createSQLQuery(SQL).executeUpdate(). It's have to be used because of lack of hint in Hibernate and also speed is important to me. Now I setup second level cache ( Ehcache ) and I was surprised, that there isn't objects in cache. Simple unit-test said, that second level cache is working, but when I put any createSQLQuery(SQL).executeUpdate(). between command, all caches were cleared. All means everything in all regions, including read-only caches. So regurally executing of "createSQLQuery(SQL).executeUpdate()" makes second level cache useless :-( I don't agree with Patrick :

...

If you know the ids of the objects you want to modify, you don´t need a bulk update operation. You can retrieve the objects from the 2nd level cache and manipulate them directly

It's a time problem to read a thousands object into memory only for deleting it.

...

it will definitely be worse than the "performance loss" of another DB round trip.

But when I've a lot of caches (read-only objects), performance is going down, because each call "executeUpdate()" needs to invalidate every cache, and maybe there is a locking problems. I thing, that Hibernate should have options to switch off second level cache cleaning, when "executeUpdate()" is called. For me this means, that this piece of code should be configurable in some way. http://viewvc.jboss.org/cgi-bin/viewvc.cgi/hibernate/core/trunk/core/src/... -------------- /** returns true if no queryspaces or if there are a match */ private boolean affectedEntity(Set querySpaces, Serializable[] entitySpaces) { if(querySpaces==null || querySpaces.isEmpty()) { return true; } ----------------

...

executeUpdate causes coarse cache invalidation ---------------------------------------------- Key: HHH-2224 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2224 Project: Hibernate Core Issue Type: Improvement Affects Versions: 3.2.0.ga Environment: Hibernate 3.2.0.ga, Oracle 9.2 Reporter: Stefan Fleiter Attachments: bulk_testcase.zip I am developing an application and want to mix bulk-updates with normal hibernate operations. The bulk updates work fine, but invalidate the whole region and I've found no possibility to prevent this. There would be 3 options to improve: - Invalidate only the modified objects if the ids where given as Query-parameters. - Let me deactivate the invalidation so I can invalidate the affected objects myself. - Transform the DML to a select to gather the objects to invalidate before executing the DML The reference documentation does not mention caching at all: http://www.hibernate.org/hib_docs/v3/reference/en/html_single/#batch-direct The best documentation I've found is: http://blog.hibernate.org/cgi-bin/blosxom.cgi/2005/07/19#dml-basic Maybe this could be added to the reference documentation... I already posted this at the forum http://forum.hibernate.org/viewtopic.php?t=966775 but did not get a single answer. I've attached a testcase for this.

Vladimir Kralik (JIRA)

Wednesday, 20 May Wed, 20 May

2:03 a.m.

New subject: [Hibernate-JIRA] Commented: (HHH-2224) executeUpdate causes coarse cache invalidation

...

All means everything in all regions, including read-only caches.

Method "executeUpdate()" clears, only DTO second level caches which are defined in mapping files ( *.hbm.xml ). Query caches ( defined by method criteria.setCacheRegion(cacheRegion) ) are not cleared/touched. So now we have strange behavior, because some caches are cleared, and some aren't. It's state as descripe Patric

...

trust me, and you will end up with hard to find bugs or stale data

...

executeUpdate causes coarse cache invalidation ---------------------------------------------- Key: HHH-2224 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2224 Project: Hibernate Core Issue Type: Improvement Affects Versions: 3.2.0.ga Environment: Hibernate 3.2.0.ga, Oracle 9.2 Reporter: Stefan Fleiter Attachments: bulk_testcase.zip I am developing an application and want to mix bulk-updates with normal hibernate operations. The bulk updates work fine, but invalidate the whole region and I've found no possibility to prevent this. There would be 3 options to improve: - Invalidate only the modified objects if the ids where given as Query-parameters. - Let me deactivate the invalidation so I can invalidate the affected objects myself. - Transform the DML to a select to gather the objects to invalidate before executing the DML The reference documentation does not mention caching at all: http://www.hibernate.org/hib_docs/v3/reference/en/html_single/#batch-direct The best documentation I've found is: http://blog.hibernate.org/cgi-bin/blosxom.cgi/2005/07/19#dml-basic Maybe this could be added to the reference documentation... I already posted this at the forum http://forum.hibernate.org/viewtopic.php?t=966775 but did not get a single answer. I've attached a testcase for this.

Vladimir Kralik (JIRA)

Thursday, 21 May Thu, 21 May

8:21 a.m.

New subject: [Hibernate-JIRA] Updated: (HHH-2224) executeUpdate causes coarse cache invalidation

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-2224?page=c... ] Vladimir Kralik updated HHH-2224: --------------------------------- Attachment: hibernate-3.2.6_p4.patch Patch for hibernate 3.2.6, which adds configuration options hibernate.cache.execute_update_clear_cache = true|false default is true true means criteria.executeUpdate() clears all caches defined in *.hbm.xml false means criteria.executeUpdate() doesn't clear caches defined in *.hbm.xml

...

executeUpdate causes coarse cache invalidation ---------------------------------------------- Key: HHH-2224 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2224 Project: Hibernate Core Issue Type: Improvement Affects Versions: 3.2.0.ga Environment: Hibernate 3.2.0.ga, Oracle 9.2 Reporter: Stefan Fleiter Attachments: bulk_testcase.zip, hibernate-3.2.6_p4.patch I am developing an application and want to mix bulk-updates with normal hibernate operations. The bulk updates work fine, but invalidate the whole region and I've found no possibility to prevent this. There would be 3 options to improve: - Invalidate only the modified objects if the ids where given as Query-parameters. - Let me deactivate the invalidation so I can invalidate the affected objects myself. - Transform the DML to a select to gather the objects to invalidate before executing the DML The reference documentation does not mention caching at all: http://www.hibernate.org/hib_docs/v3/reference/en/html_single/#batch-direct The best documentation I've found is: http://blog.hibernate.org/cgi-bin/blosxom.cgi/2005/07/19#dml-basic Maybe this could be added to the reference documentation... I already posted this at the forum http://forum.hibernate.org/viewtopic.php?t=966775 but did not get a single answer. I've attached a testcase for this.

Ioannis Cherouvim (JIRA)

Tuesday, 26 May Tue, 26 May

9:29 a.m.

New subject: [Hibernate-JIRA] Commented: (HHH-2224) executeUpdate causes coarse cache invalidation

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-2224?page=c... ] Ioannis Cherouvim commented on HHH-2224: ---------------------------------------- As Vladimir said:

...

I thing, that Hibernate should have options to switch off second level cache cleaning, when "executeUpdate()" is called.

I'd like that as well.

...

executeUpdate causes coarse cache invalidation ---------------------------------------------- Key: HHH-2224 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2224 Project: Hibernate Core Issue Type: Improvement Affects Versions: 3.2.0.ga Environment: Hibernate 3.2.0.ga, Oracle 9.2 Reporter: Stefan Fleiter Attachments: bulk_testcase.zip, hibernate-3.2.6_p4.patch I am developing an application and want to mix bulk-updates with normal hibernate operations. The bulk updates work fine, but invalidate the whole region and I've found no possibility to prevent this. There would be 3 options to improve: - Invalidate only the modified objects if the ids where given as Query-parameters. - Let me deactivate the invalidation so I can invalidate the affected objects myself. - Transform the DML to a select to gather the objects to invalidate before executing the DML The reference documentation does not mention caching at all: http://www.hibernate.org/hib_docs/v3/reference/en/html_single/#batch-direct The best documentation I've found is: http://blog.hibernate.org/cgi-bin/blosxom.cgi/2005/07/19#dml-basic Maybe this could be added to the reference documentation... I already posted this at the forum http://forum.hibernate.org/viewtopic.php?t=966775 but did not get a single answer. I've attached a testcase for this.

Andrej (JIRA)

Thursday, 7 January Thu, 7 Jan

12:19 a.m.

New subject: [Hibernate-JIRA] Commented: (HHH-2224) executeUpdate causes coarse cache invalidation

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-2224?page=c... ] Andrej commented on HHH-2224: ----------------------------- I could not find this anywhere documented and just lost two days finding out why my caches are being inverted. Yes it makes sense, but I opt for a configuration option too. The option hibernate.cache.execute_update_clear_cache does not work in Hibernate 3.3.1. Is the patch applied to the official release branch?

...

executeUpdate causes coarse cache invalidation ---------------------------------------------- Key: HHH-2224 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2224 Project: Hibernate Core Issue Type: Improvement Affects Versions: 3.2.0.ga Environment: Hibernate 3.2.0.ga, Oracle 9.2 Reporter: Stefan Fleiter Attachments: bulk_testcase.zip, hibernate-3.2.6_p4.patch I am developing an application and want to mix bulk-updates with normal hibernate operations. The bulk updates work fine, but invalidate the whole region and I've found no possibility to prevent this. There would be 3 options to improve: - Invalidate only the modified objects if the ids where given as Query-parameters. - Let me deactivate the invalidation so I can invalidate the affected objects myself. - Transform the DML to a select to gather the objects to invalidate before executing the DML The reference documentation does not mention caching at all: http://www.hibernate.org/hib_docs/v3/reference/en/html_single/#batch-direct The best documentation I've found is: http://blog.hibernate.org/cgi-bin/blosxom.cgi/2005/07/19#dml-basic Maybe this could be added to the reference documentation... I already posted this at the forum http://forum.hibernate.org/viewtopic.php?t=966775 but did not get a single answer. I've attached a testcase for this.

Ivan Tarapon (JIRA)

Friday, 8 January Fri, 8 Jan

2:27 a.m.

New subject: [Hibernate-JIRA] Commented: (HHH-2224) executeUpdate causes coarse cache invalidation

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-2224?page=c... ] Ivan Tarapon commented on HHH-2224: -----------------------------------

...

The option hibernate.cache.execute_update_clear_cache does not work in Hibernate 3.3.1. Is the patch applied to the official release branch?

no. it doesn't

...

executeUpdate causes coarse cache invalidation ---------------------------------------------- Key: HHH-2224 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2224 Project: Hibernate Core Issue Type: Improvement Affects Versions: 3.2.0.ga Environment: Hibernate 3.2.0.ga, Oracle 9.2 Reporter: Stefan Fleiter Attachments: bulk_testcase.zip, hibernate-3.2.6_p4.patch I am developing an application and want to mix bulk-updates with normal hibernate operations. The bulk updates work fine, but invalidate the whole region and I've found no possibility to prevent this. There would be 3 options to improve: - Invalidate only the modified objects if the ids where given as Query-parameters. - Let me deactivate the invalidation so I can invalidate the affected objects myself. - Transform the DML to a select to gather the objects to invalidate before executing the DML The reference documentation does not mention caching at all: http://www.hibernate.org/hib_docs/v3/reference/en/html_single/#batch-direct The best documentation I've found is: http://blog.hibernate.org/cgi-bin/blosxom.cgi/2005/07/19#dml-basic Maybe this could be added to the reference documentation... I already posted this at the forum http://forum.hibernate.org/viewtopic.php?t=966775 but did not get a single answer. I've attached a testcase for this.

Daniel Grove (JIRA)

Tuesday, 29 June Tue, 29 Jun

6:49 p.m.

New subject: [Hibernate-JIRA] Commented: (HHH-2224) executeUpdate causes coarse cache invalidation

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-2224?page=c... ] Daniel Grove commented on HHH-2224: ----------------------------------- This is a major problem for our system right now because we use transactional JBoss Cache with optimistic locking. None of our second-level cache objects are related to the bulk updates, but regardless all entity cache is cleared. This often causes failures because another transaction has made changes to an entity in the cache. Are there any hopes for a patch? Does anyone know of a workaround? Thanks, Daniel

...

executeUpdate causes coarse cache invalidation ---------------------------------------------- Key: HHH-2224 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2224 Project: Hibernate Core Issue Type: Improvement Affects Versions: 3.2.0.ga Environment: Hibernate 3.2.0.ga, Oracle 9.2 Reporter: Stefan Fleiter Attachments: bulk_testcase.zip, hibernate-3.2.6_p4.patch I am developing an application and want to mix bulk-updates with normal hibernate operations. The bulk updates work fine, but invalidate the whole region and I've found no possibility to prevent this. There would be 3 options to improve: - Invalidate only the modified objects if the ids where given as Query-parameters. - Let me deactivate the invalidation so I can invalidate the affected objects myself. - Transform the DML to a select to gather the objects to invalidate before executing the DML The reference documentation does not mention caching at all: http://www.hibernate.org/hib_docs/v3/reference/en/html_single/#batch-direct The best documentation I've found is: http://blog.hibernate.org/cgi-bin/blosxom.cgi/2005/07/19#dml-basic Maybe this could be added to the reference documentation... I already posted this at the forum http://forum.hibernate.org/viewtopic.php?t=966775 but did not get a single answer. I've attached a testcase for this.

Ioannis Cherouvim (JIRA)

10:57 p.m.

New subject: [Hibernate-JIRA] Commented: (HHH-2224) executeUpdate causes coarse cache invalidation

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-2224?page=c... ] Ioannis Cherouvim commented on HHH-2224: ---------------------------------------- @Daniel: I use a direct JDBC connection to avoid session invalidation of everything. It works, but of course this is not nice. {code} Connection con = getSession().connection(); PreparedStatement s = con.prepareStatement("update articles set bar=?"); s.setString(1, "foo"); s.executeUpdate(); con.commit(); {code}

...

executeUpdate causes coarse cache invalidation ---------------------------------------------- Key: HHH-2224 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2224 Project: Hibernate Core Issue Type: Improvement Affects Versions: 3.2.0.ga Environment: Hibernate 3.2.0.ga, Oracle 9.2 Reporter: Stefan Fleiter Attachments: bulk_testcase.zip, hibernate-3.2.6_p4.patch I am developing an application and want to mix bulk-updates with normal hibernate operations. The bulk updates work fine, but invalidate the whole region and I've found no possibility to prevent this. There would be 3 options to improve: - Invalidate only the modified objects if the ids where given as Query-parameters. - Let me deactivate the invalidation so I can invalidate the affected objects myself. - Transform the DML to a select to gather the objects to invalidate before executing the DML The reference documentation does not mention caching at all: http://www.hibernate.org/hib_docs/v3/reference/en/html_single/#batch-direct The best documentation I've found is: http://blog.hibernate.org/cgi-bin/blosxom.cgi/2005/07/19#dml-basic Maybe this could be added to the reference documentation... I already posted this at the forum http://forum.hibernate.org/viewtopic.php?t=966775 but did not get a single answer. I've attached a testcase for this.

Steve Ebersole (JIRA)

Wednesday, 30 June Wed, 30 Jun

4:03 p.m.

New subject: [Hibernate-JIRA] Commented: (HHH-2224) executeUpdate causes coarse cache invalidation

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-2224?page=c... ] Steve Ebersole commented on HHH-2224: ------------------------------------- Patrick is spot on. There really is no other option here. I am not going to add an option that allows developers to tell Hibernate to leave itself in an inconsistent state. Now, could we perhaps allow a means to plug in a different behavior in "bulk operation cleanup". The concern is applications/developers leveraging that and then the Hibernate team having to deal with bug reports when erroneous stuff starts getting returned because it was not properly invalidated from the second level cache regions during some custom "bulk operation cleanup".

...

executeUpdate causes coarse cache invalidation ---------------------------------------------- Key: HHH-2224 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2224 Project: Hibernate Core Issue Type: Improvement Affects Versions: 3.2.0.ga Environment: Hibernate 3.2.0.ga, Oracle 9.2 Reporter: Stefan Fleiter Attachments: bulk_testcase.zip, hibernate-3.2.6_p4.patch I am developing an application and want to mix bulk-updates with normal hibernate operations. The bulk updates work fine, but invalidate the whole region and I've found no possibility to prevent this. There would be 3 options to improve: - Invalidate only the modified objects if the ids where given as Query-parameters. - Let me deactivate the invalidation so I can invalidate the affected objects myself. - Transform the DML to a select to gather the objects to invalidate before executing the DML The reference documentation does not mention caching at all: http://www.hibernate.org/hib_docs/v3/reference/en/html_single/#batch-direct The best documentation I've found is: http://blog.hibernate.org/cgi-bin/blosxom.cgi/2005/07/19#dml-basic Maybe this could be added to the reference documentation... I already posted this at the forum http://forum.hibernate.org/viewtopic.php?t=966775 but did not get a single answer. I've attached a testcase for this.

Steve Ebersole (JIRA)

4:08 p.m.

New subject: [Hibernate-JIRA] Commented: (HHH-2224) executeUpdate causes coarse cache invalidation

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-2224?page=c... ] Steve Ebersole commented on HHH-2224: ------------------------------------- The blog urls reference the old blog software. iirc the blog post being referenced is either http://in.relation.to/Bloggers/BulkOperations or http://in.relation.to/Bloggers/MultitableBulkOperations. Probably http://in.relation.to/Bloggers/BulkOperations since that does have a section discussing the impact on caching {quote} Upon completion of a "Bulk Operation", Hibernate invalidates any needed region(s) within the shared cache to maintain consistency. It has to be done through invalidation because the UPDATE or DELETE is executed solely on the database server; thus Hibernate has no idea about the ids of any affected entities, nor (in the case of updates) what the new state might be. {quote}

...

executeUpdate causes coarse cache invalidation ---------------------------------------------- Key: HHH-2224 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2224 Project: Hibernate Core Issue Type: Improvement Affects Versions: 3.2.0.ga Environment: Hibernate 3.2.0.ga, Oracle 9.2 Reporter: Stefan Fleiter Attachments: bulk_testcase.zip, hibernate-3.2.6_p4.patch I am developing an application and want to mix bulk-updates with normal hibernate operations. The bulk updates work fine, but invalidate the whole region and I've found no possibility to prevent this. There would be 3 options to improve: - Invalidate only the modified objects if the ids where given as Query-parameters. - Let me deactivate the invalidation so I can invalidate the affected objects myself. - Transform the DML to a select to gather the objects to invalidate before executing the DML The reference documentation does not mention caching at all: http://www.hibernate.org/hib_docs/v3/reference/en/html_single/#batch-direct The best documentation I've found is: http://blog.hibernate.org/cgi-bin/blosxom.cgi/2005/07/19#dml-basic Maybe this could be added to the reference documentation... I already posted this at the forum http://forum.hibernate.org/viewtopic.php?t=966775 but did not get a single answer. I've attached a testcase for this.

Ioannis Cherouvim (JIRA)

5:13 p.m.

New subject: [Hibernate-JIRA] Commented: (HHH-2224) executeUpdate causes coarse cache invalidation

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-2224?page=c... ] Ioannis Cherouvim commented on HHH-2224: ---------------------------------------- @Steve Ebersole: And what if you do allow it? The programmer will be fully responsible for any problem caused. Is it better that we now need to use plain sql to avoid this behavior?

...

executeUpdate causes coarse cache invalidation ---------------------------------------------- Key: HHH-2224 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2224 Project: Hibernate Core Issue Type: Improvement Affects Versions: 3.2.0.ga Environment: Hibernate 3.2.0.ga, Oracle 9.2 Reporter: Stefan Fleiter Attachments: bulk_testcase.zip, hibernate-3.2.6_p4.patch I am developing an application and want to mix bulk-updates with normal hibernate operations. The bulk updates work fine, but invalidate the whole region and I've found no possibility to prevent this. There would be 3 options to improve: - Invalidate only the modified objects if the ids where given as Query-parameters. - Let me deactivate the invalidation so I can invalidate the affected objects myself. - Transform the DML to a select to gather the objects to invalidate before executing the DML The reference documentation does not mention caching at all: http://www.hibernate.org/hib_docs/v3/reference/en/html_single/#batch-direct The best documentation I've found is: http://blog.hibernate.org/cgi-bin/blosxom.cgi/2005/07/19#dml-basic Maybe this could be added to the reference documentation... I already posted this at the forum http://forum.hibernate.org/viewtopic.php?t=966775 but did not get a single answer. I've attached a testcase for this.

Vladimir Kralik (JIRA)

Thursday, 1 July Thu, 1 Jul

1:57 a.m.

New subject: [Hibernate-JIRA] Commented: (HHH-2224) executeUpdate causes coarse cache invalidation

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-2224?page=c... ] Vladimir Kralik commented on HHH-2224: -------------------------------------- Steve said : """I am not going to add an option that allows developers to tell Hibernate to leave itself in an inconsistent state.""" Developers are enough smarty to find path which by-pass this barrier. ( for example by using connection/datasource directly ). So the main idea "don't allow developers leave Hibernate cache in inconsistent state" is only desire. I think, that much better is to have this option, and don't force developers to by-pass this barrier and give them information, how hibernate works with second-level cache. Default value should be "clear all caches after each executeUpdate()" As I said one year ago, I've mostly use read-only caches, so I really don't want to clear this caches after each executeUpdate-method. Read-only caches means, that I've tables in database ( codelists ), which aren't maintained by application/Hibernate, but directly in database. I still use Hibernate 3.2.6 with my own patches, because Hibernate bug-fixing is very slow process.

...

executeUpdate causes coarse cache invalidation ---------------------------------------------- Key: HHH-2224 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2224 Project: Hibernate Core Issue Type: Improvement Affects Versions: 3.2.0.ga Environment: Hibernate 3.2.0.ga, Oracle 9.2 Reporter: Stefan Fleiter Attachments: bulk_testcase.zip, hibernate-3.2.6_p4.patch I am developing an application and want to mix bulk-updates with normal hibernate operations. The bulk updates work fine, but invalidate the whole region and I've found no possibility to prevent this. There would be 3 options to improve: - Invalidate only the modified objects if the ids where given as Query-parameters. - Let me deactivate the invalidation so I can invalidate the affected objects myself. - Transform the DML to a select to gather the objects to invalidate before executing the DML The reference documentation does not mention caching at all: http://www.hibernate.org/hib_docs/v3/reference/en/html_single/#batch-direct The best documentation I've found is: http://blog.hibernate.org/cgi-bin/blosxom.cgi/2005/07/19#dml-basic Maybe this could be added to the reference documentation... I already posted this at the forum http://forum.hibernate.org/viewtopic.php?t=966775 but did not get a single answer. I've attached a testcase for this.

Steve Ebersole (JIRA)

Thursday, 8 July Thu, 8 Jul

1:41 p.m.

New subject: [Hibernate-JIRA] Commented: (HHH-2224) executeUpdate causes coarse cache invalidation

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-2224?page=c... ] Steve Ebersole commented on HHH-2224: ------------------------------------- Vladimir, there is a significant difference between Hibernate allowing a certain (incorrect) behavior and developers achieving this behavior by "[finding a] path which by-pass this barrier". Namely in the first case the implication is that Hibernate supports such a (incorrect) behavior, condones it even. How do you correlate a read-only cache and things that can be updated? Ioannis, as I said I am not ruling out a pluggable strategy where developers could themselves choose this behavior. There is, again, a significant difference between Hibernate providing the option to enable this behavior via switch etc versus it providing the ability for developers to plug in this behavior. And trust me, if we go this route, we will see bug reports here about how Hibernate served up incorrect cached results because the user developed a bad pluggable "bulk operation cleanup" strategy. I assume I can send them to you for a lecture on how they "are fully responsible"? ;)

...

executeUpdate causes coarse cache invalidation ---------------------------------------------- Key: HHH-2224 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2224 Project: Hibernate Core Issue Type: Improvement Affects Versions: 3.2.0.ga Environment: Hibernate 3.2.0.ga, Oracle 9.2 Reporter: Stefan Fleiter Attachments: bulk_testcase.zip, hibernate-3.2.6_p4.patch I am developing an application and want to mix bulk-updates with normal hibernate operations. The bulk updates work fine, but invalidate the whole region and I've found no possibility to prevent this. There would be 3 options to improve: - Invalidate only the modified objects if the ids where given as Query-parameters. - Let me deactivate the invalidation so I can invalidate the affected objects myself. - Transform the DML to a select to gather the objects to invalidate before executing the DML The reference documentation does not mention caching at all: http://www.hibernate.org/hib_docs/v3/reference/en/html_single/#batch-direct The best documentation I've found is: http://blog.hibernate.org/cgi-bin/blosxom.cgi/2005/07/19#dml-basic Maybe this could be added to the reference documentation... I already posted this at the forum http://forum.hibernate.org/viewtopic.php?t=966775 but did not get a single answer. I've attached a testcase for this.

rajesh kumar (JIRA)

11:57 p.m.

New subject: [Hibernate-JIRA] Commented: (HHH-2224) executeUpdate causes coarse cache invalidation

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-2224?page=c... ] rajesh kumar commented on HHH-2224: ----------------------------------- Hi All, I have found a solution to the problem described. Hibernate provides a <synchronize> tag to specify what all are the tables that are affected becuase of the bulkupdate. If we are specifying the <synchronize>with table name hibernate only invlidate the cache of the table present in the synchronize table.This will avoid clearning of all the cache regions including the read only cache. For achieving this, <synchronize> should be added to the <sql-query> during a bulk update or a delete. Eg: <sql-query name="queryname"> <synchronize table="tablename"/> update tablename set value = ? </sql-query> The synchronization should be done on the affected tables because of the update. There can be one or more synchronize tags within the same block depending on what all tables got affected. This will result in cache invalidation of only those tables which are synchronized; otherwise the entire cache region is invalidated. Note: Hibernate does a flush of the pending data for synchronized tables (from insert/update queue) before actually doing the synchronization. So the flush is triggered automatically for those data in the insert/update/delete queues where the affected tables are synchronized. We could get this documented in hibernate reference documentation.

...

executeUpdate causes coarse cache invalidation ---------------------------------------------- Key: HHH-2224 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2224 Project: Hibernate Core Issue Type: Improvement Affects Versions: 3.2.0.ga Environment: Hibernate 3.2.0.ga, Oracle 9.2 Reporter: Stefan Fleiter Attachments: bulk_testcase.zip, hibernate-3.2.6_p4.patch I am developing an application and want to mix bulk-updates with normal hibernate operations. The bulk updates work fine, but invalidate the whole region and I've found no possibility to prevent this. There would be 3 options to improve: - Invalidate only the modified objects if the ids where given as Query-parameters. - Let me deactivate the invalidation so I can invalidate the affected objects myself. - Transform the DML to a select to gather the objects to invalidate before executing the DML The reference documentation does not mention caching at all: http://www.hibernate.org/hib_docs/v3/reference/en/html_single/#batch-direct The best documentation I've found is: http://blog.hibernate.org/cgi-bin/blosxom.cgi/2005/07/19#dml-basic Maybe this could be added to the reference documentation... I already posted this at the forum http://forum.hibernate.org/viewtopic.php?t=966775 but did not get a single answer. I've attached a testcase for this.

Vladimir Kralik (JIRA)

Friday, 9 July Fri, 9 Jul

1:34 a.m.

New subject: [Hibernate-JIRA] Commented: (HHH-2224) executeUpdate causes coarse cache invalidation

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-2224?page=c... ] Vladimir Kralik commented on HHH-2224: -------------------------------------- 2 Steve : This behaviour should be documented a switched off by default, and senior developer can make decision, if he switches it on. I would like to have this possibility. Why do you thing, that this behaviour is incorrect ? There is a lot of ways how to update data outside of hibernate ( for example : triggers ), so the senior developer have to remember for which table can use cache and for which cannot. I've a big database ( 1TB ), about 400 users and 10 application servers in cluster, changes are going too quickly, so I've caches only for several codelist tables.

...

How do you correlate a read-only cache and things that can be updated?

Things that can be updated don't have cache. Cached read-only tables/codelists are changed (only operations are INSERT and UPDATE of valid_to-column ) during system maintainance time. 2 rajesh : Your solution is not for me, because I don't have SQL-query extracted outside java-code. I compute this query inside of application.

...

executeUpdate causes coarse cache invalidation ---------------------------------------------- Key: HHH-2224 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2224 Project: Hibernate Core Issue Type: Improvement Affects Versions: 3.2.0.ga Environment: Hibernate 3.2.0.ga, Oracle 9.2 Reporter: Stefan Fleiter Attachments: bulk_testcase.zip, hibernate-3.2.6_p4.patch I am developing an application and want to mix bulk-updates with normal hibernate operations. The bulk updates work fine, but invalidate the whole region and I've found no possibility to prevent this. There would be 3 options to improve: - Invalidate only the modified objects if the ids where given as Query-parameters. - Let me deactivate the invalidation so I can invalidate the affected objects myself. - Transform the DML to a select to gather the objects to invalidate before executing the DML The reference documentation does not mention caching at all: http://www.hibernate.org/hib_docs/v3/reference/en/html_single/#batch-direct The best documentation I've found is: http://blog.hibernate.org/cgi-bin/blosxom.cgi/2005/07/19#dml-basic Maybe this could be added to the reference documentation... I already posted this at the forum http://forum.hibernate.org/viewtopic.php?t=966775 but did not get a single answer. I've attached a testcase for this.

rajesh kumar (JIRA)

5:21 a.m.

New subject: [Hibernate-JIRA] Commented: (HHH-2224) executeUpdate causes coarse cache invalidation

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-2224?page=c... ] rajesh kumar commented on HHH-2224: ----------------------------------- if you are computing the query inside java application the I hope you are using org.hibernate.SQLQuery object fon r executing the query. In that case you could use any of the following method to acheive the same thing. SQLQuery SQLQuery.addSynchronizedQuerySpace(String querySpace) Adds a query space for auto-flush synchronization. SQLQuery SQLQuery.addSynchronizedEntityName(String entityName) Adds an entity name or auto-flush synchronization. SQLQuery SQLQuery.addSynchronizedEntityClass(Class entityClass) Adds an entity name or auto-flush synchronization.

...

executeUpdate causes coarse cache invalidation ---------------------------------------------- Key: HHH-2224 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2224 Project: Hibernate Core Issue Type: Improvement Affects Versions: 3.2.0.ga Environment: Hibernate 3.2.0.ga, Oracle 9.2 Reporter: Stefan Fleiter Attachments: bulk_testcase.zip, hibernate-3.2.6_p4.patch I am developing an application and want to mix bulk-updates with normal hibernate operations. The bulk updates work fine, but invalidate the whole region and I've found no possibility to prevent this. There would be 3 options to improve: - Invalidate only the modified objects if the ids where given as Query-parameters. - Let me deactivate the invalidation so I can invalidate the affected objects myself. - Transform the DML to a select to gather the objects to invalidate before executing the DML The reference documentation does not mention caching at all: http://www.hibernate.org/hib_docs/v3/reference/en/html_single/#batch-direct The best documentation I've found is: http://blog.hibernate.org/cgi-bin/blosxom.cgi/2005/07/19#dml-basic Maybe this could be added to the reference documentation... I already posted this at the forum http://forum.hibernate.org/viewtopic.php?t=966775 but did not get a single answer. I've attached a testcase for this.

5280

days inactive

6618

days old

hibernate-issues@lists.jboss.org

Manage subscription

19 comments

10 participants

tags (0)

participants (10)

Andrej (JIRA)
Daniel Grove (JIRA)
Ioannis Cherouvim (JIRA)
Ivan Tarapon (JIRA)
Karl Smola (JIRA)
Patrick Kranz (JIRA)
rajesh kumar (JIRA)
Stefan Fleiter (JIRA)
Steve Ebersole (JIRA)
Vladimir Kralik (JIRA)

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

[Hibernate-JIRA] Erstellt: (HHH-2224) executeUpdate causes coarse cache invalidation