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

Sanne Grinovero (JIRA) noreply at atlassian.com
Thu May 19 11:47:25 EDT 2011


    [ http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=42353#action_42353 ] 

Sanne Grinovero commented on HSEARCH-679:
-----------------------------------------

Hi Adam,
thanks for the report. I guess only B is @Indexed right?
About use case #1, changing the value of the Collection<B> will require a re-indexing of each B instance which was in the collection before, or after. Remember an index is not update-able, so we have to rebuilt the index line for each B instance from scratch.
Use case #2 should NOT trigger indexing however, unless A is being annotated with _ at DynamicBoost_ or _ at ClassBridge_; if that's not the case, could you please provide a test case? I'll be glad to look into it. To create one, please have a look at what Tom and me created for this issue: _org.hibernate.search.test.engine.optimizations.CollectionUpdateEventTest_, it would be nice to patch that to cover your case as well.

> Entity whose related entity collection is updated causes loading of @ContainedIn entities
> -----------------------------------------------------------------------------------------
>
>                 Key: HSEARCH-679
>                 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-679
>             Project: Hibernate Search
>          Issue Type: Bug
>          Components: engine
>    Affects Versions: 3.2.1, 3.3.0.Final
>         Environment: Hibernate 3.6.1-SNAPSHOT/Hibernate Search 3.4.0-SNAPSHOT and Hibernate 3.5.6/Hibernate Search 3.2.1
>            Reporter: Tom Waterhouse
>            Assignee: Sanne Grinovero
>             Fix For: 3.4.0.CR2
>
>         Attachments: HSEARCH-679-test-updated.zip, HSEARCH-679-test.zip, HSEARCH-679.zip
>
>
> This problem seems related to HSEARCH-361.  An entity that references another entity as @ContainedIn is causing the load of entities related to the other entity.  
> Using the model below, the update of the collection of D instances in the class C causes the load of related classes B and A.
> {code}
> public class A {
>    @Field
>    private String name;
>    @IndexEmbedded
>    private B
> }
> {code}
> {code}
> public class B {
>    @ContainedIn
>    private A a;
>    @IndexEmbedded
>    private C c;
> }
> {code}
> {code}
> public class C {
>    @ContainedIn
>    private Collection<B> b;
>    // NOT INDEXED
>    private Collection<D> d;
> }
> {code}
> {code}
> public class D {
>    public String value;
> }
> {code}

-- 
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.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


More information about the hibernate-issues mailing list