[hibernate-issues] [Hibernate-JIRA] Commented: (HSEARCH-767) REGRESSION: Reindexing of @ContainedIn entities fail under certain conditions

Kyrill Alyoshin (JIRA) noreply at atlassian.com
Thu May 19 08:35:25 EDT 2011


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

Kyrill Alyoshin commented on HSEARCH-767:
-----------------------------------------

No problem, Sanne. I was actually expecting you to reject it for the same reason. The workaround is obviously version easy, just re-attach the parent back to session. I am just surprised it worked before. All in all, it would nice to have a detailed tutorial for the general user population on Hibernate event model. Just to see which events are fired when. Maybe there is one already in existence?..

> REGRESSION: Reindexing of @ContainedIn entities fail under certain conditions
> -----------------------------------------------------------------------------
>
>                 Key: HSEARCH-767
>                 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-767
>             Project: Hibernate Search
>          Issue Type: Bug
>          Components: engine
>    Affects Versions: 3.4.0.Final
>            Reporter: Kyrill Alyoshin
>         Attachments: hibernate_search_bug.zip
>
>
> So, I've just upgraded to 3.4.0 from 3.3.0, and one of my Hibernate Search tests fails. Here is the summary.
> Let's say we have a project with two entities: Parent and Child. Let's create first Parent with a Child and a second Parent with a Child. Transaction commits. Parent is @Indexed, Child is @IndexedEmbedded. 
> Now, in a separate transaction, we retrieve the child of Parent 1, and move it to Parent 2. Parent 2 is detached (!). Parent 2 will fail to be re-indexed. Of course, if we re-associate Parent 2 with session, it will work. But it used to work without this. I've reproduced the problem in the attached test case. 
> I am really curious as what you're going to do about this bug. :-)

-- 
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