[hibernate-issues] [Hibernate-JIRA] Issue Comment Edited: (HSEARCH-679) Entity whose related entity collection is updated causes loading of @ContainedIn entities

[ http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-679?pag... ] Adam Harris edited comment on HSEARCH-679 at 5/19/11 10:02 AM: --------------------------------------------------------------- I'm running Hibernate Search 3.4.0.Final with Hibernate Core 3.6.3.Final, and this doesn't appear to be fixed. Perhaps I have another corner-case that isn't accounted for in this patch. Here is my model: {code:java} public class A { @Field private String name; @ContainedIn private Collection<B> b; private A parent; // Not indexed private Collection<A> children; // Not indexed } {code} {code:java} public class B { @IndexEmbedded private A a; } {code} USE CASE #1 If I add a new instance of B to A's collection, the only change to A is the row version is incremented. This not only leads to Hibernate Search updating the index for A, but then it cascades to all of the B's in the collection even though there is nothing to change. USE CASE #2 In addition, if I add a new instance of A to A's "children" collection (which this hierarchy isn't even represented in the index), it performs all the same index updates as USE CASE #1. For simplicity, I've eliminated some other classes that are referenced in class B, but this problem results in an explosion of objects being unnecessarily loaded from the DB and indexes updated with zero new information. was (Author: aharris): I'm running Hibernate Search 3.4.0.Final with Hibernate Core 3.6.3.Final, and this doesn't appear to be fixed. Perhaps I have another corner-case that isn't accounted for in this patch. Here is my model: public class A { @Field private String name; @ContainedIn private Collection<B> b; private A parent; // Not indexed private Collection<A> children; // Not indexed } public class B { @IndexEmbedded private A a; } USE CASE #1 If I add a new instance of B to A's collection, the only change to A is the row version is incremented. This not only leads to Hibernate Search updating the index for A, but then it cascades to all of the B's in the collection even though there is nothing to change. USE CASE #2 In addition, if I add a new instance of A to A's "children" collection (which this hierarchy isn't even represented in the index), it performs all the same index updates as USE CASE #1. For simplicity, I've eliminated some other classes that are referenced in class B, but this problem results in an explosion of objects being unnecessarily loaded from the DB and indexes updated with zero new information. -- 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