[hibernate-issues] [Hibernate-JIRA] Commented: (HSEARCH-513) Experiencing long delays when indexing entities saved in different transactions

[Florin Haizea (JIRA)]

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

Florin Haizea commented on HSEARCH-513:
---------------------------------------

Hi Amin,

 While dealing with other issues that I had with hibernate search I tried to see if implementing equals and hashCode would solve those issues. I implemented equals the way you did and I found out that not all the entities are being indexed. Lets say we have a Person which has a set of Name(s). If we use equals the way you did, only comparing the ids, then all the non persisted names are equal to each other because their ids are null. Thus if we create a Person and add 20 names to its names set, in the end, the names set will contain only one name. This is obviously a problem, both for the application logic, as only 1 name is saved instead of 20, and for the hibernate searching as only one name is being indexed instead of 20.

 Here is a relevant article: http://community.jboss.org/wiki/EqualsandHashCode

 Taking this into account, I guess that why equals and hashCode solve the batch time problem is simply because hibernate search does not index all the relationships of an entity. So instead of solving the bug, this only hides it. I did not verify this but this is what I think it happens.

> Experiencing long delays when indexing entities saved in different transactions
> -------------------------------------------------------------------------------
>
>                 Key: HSEARCH-513
>                 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-513
>             Project: Hibernate Search
>          Issue Type: Bug
>          Components: engine
>    Affects Versions: 3.2.0.CR1
>         Environment: Hibernate 3.5.1-Final
> Spring 3.0.2
> MySQL Connector 5.1.6
>            Reporter: Florin Haizea
>             Fix For: 3.3.0
>
>         Attachments: AllLibsExceptSpringAndHibernate.zip, build.xml, hibernate-search-jms.zip, hibernate3.jar, HibernateSearchJira.zip, output.txt, output08052010.rtf, SpringAndHibernateLibs.zip
>
>
> https://forum.hibernate.org/viewtopic.php?f=9&t=1003224
> I have 3 entities Person, Event and ParentOfBirthEvent. I save about 8000 Person objects in batches of 20, each batch is being saved in a different transaction. After a sufficient number of entities have been persisted (the saving and indexing of initial batches takes between150ms and 500ms) the indexing of the entities that are saved in some of the following batches takes a very large amount of time (sometime even minutes for a whole batch).
> The problem is that in order for these delays to appear there has to be a certain relationship between the objects saved in the current batch and objects saved in previous batches. The only way in which I can reproduce this 100% is by importing a file (which was submitted by one of the users of our app), creating entities based on the data in that file and saving the entities in batches of 20. When I reach batch number 273 or so the indexing starts taking a lot of time.
> If I removed the @IndexedEmbedded annotation from the "parent" field in the ParentOfBirthEvent class the problem is solved. Also, if I removed all the hibernate search listeners from the sessionFactory the problem is solved.

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