Ahhh
In theory it should not as Hibernate Search reads data in the
beforeCompletion phase.
Unless people do not apply changes in a transaction in which case we
need to execute the read in the post* event.
We will check whether or not people use surrounding transactions
(Hibernate aware Tx either through JTA or via the direct Hibernate
Transaction API).
Alternatively, is it possible to move the post* event after the flush?
Or create noew events for that? That would solve everybody's issue.
Emmanuel
On Mar 5, 2009, at 22:54, Steve Ebersole wrote:
Is this somehow different than the "attempt to load stuff into the PC
during flush" scenarios I see in any of these related issues?
-
Steve Ebersole
Project Lead
http://hibernate.org
st...@hibernate.org
Principal Software Engineer
JBoss, a division of Red Hat
http://jboss.com
http://redhat.com
steve.ebers...@jboss.com
steve.ebers...@redhat.com
On Thu, 2009-03-05 at 19:14 -0500, Emmanuel Bernard wrote:
http://opensource.atlassian.com/projects/hibernate/browse/HHH-3225
Steve, any chance you could look at this one, it seems to hit HSearch
users on a regular basis.
_______________________________________________
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
_______________________________________________
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
