Message Title

Sanne Grinovero commented on an issue

There is an additional conceptual problem. Hibernate ORM might have flushed changes to the database before you run the Session.clear(), at that point if the transaction is committed, changes on the database which where flushed will apply.
You don't want to clear the indexing tasks at that point.

I think we need to listen to Session.flush() events too, so to automate the "right" decision to be taken.

Add Comment

Hibernate Search /

HSEARCH-1270

I have a use-case with a nested transaction in a loop.

When the nested transaction is committed, I manually flush and clear the Hibernate-Session, because otherwise, the program would run into an {{OutOfMemoryException}}, because it loads to many objects into the Hibernate session.

Sometimes, the nested transaction is rolled back, to cancel some wor...

This message was sent by Atlassian JIRA