[
http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-513?pag...
]
Hardy Ferentschik commented on HSEARCH-513:
-------------------------------------------
Looking at the entities a little closer I am wondering what you try to achieve. For
example, you have a {{Person}} which has an {{Event}} 'birthEvent'. In the
{{Event}} class you then have a set of {{Person}} 'children' and a set of
{{ParentOfBirthEvent}} 'parentsOf'. And there is also a
'parentOfBirthEvents' in {{Person}} itself. All associations are annotated with
@IndexedEmbedded and @ContainedIn. Are you sure you are not just running in a cyclic
dependency during indexing.
In {{Person}} you specify once the depth attribute using '4' as value. Why
'4'? What queries are you expecting to run against this index and have you used
Luke to actually inspect which Document fields are getting added?
Given that removing @IndexedEmbedded seems to fix your problem my guess is at the moment
that you have a cyclic dependency during indexing.
Hibernate Search 3.2.0.CR1 listeners cause 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
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.2.0
Attachments: AllLibsExceptSpringAndHibernate.zip, HibernateSearchJira.zip,
SpringAndHibernateLibs.zip
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....
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira