Thanks you for your feedback. Since this is not an issue with Hibernate, but rather with how it's used, I will close this ticket.

In order to make Hibernate Search easier to use and to reduce the impact of this problem, I opened two tickets for Hibernate Search 6:

• HSEARCH-3303 Open to document the "batching" use case and explain how it should be implemented when Hibernate Search is involved.
• HSEARCH-3360 Open to at least avoid LazyInitializationExceptions when applying the <make changes> ; flush(); clear(); <repeat> pattern. We will potentially have an OutOfMemoryException in some cases (since the index work cache will not be flushed before the end of the transaction) , but that may be easier to debug for users.