Indexing issue while committing: log error instead of throwing exception?

Hibernate Search
5

@gsmet
You are right, these issues should not happen in the first place. Currently, this happes during a larger entity import where the persistence context might be cleared in between, I have to figure out what happens here as debugging this is really tricky (it only does not work in one specific application which a specific set of data - the import works fine in three of our test applications). In the current situation, the import cannot be finished at all, even though it is fully acceptable to have an inconsistent full text index here.

Basically, I just want to have some safety net as I want to ensure that the user can continue his work at the cost of an inconsistent full text index.

In addition, what also could be improved is stack traces like this: (at least in Hibernate Search 5.3, we’re migrating to 5.9 soon)

Caused by: org.hibernate.LazyInitializationException: could not initialize proxy - no Session
	at org.hibernate.proxy.AbstractLazyInitializer.initialize(AbstractLazyInitializer.java:165)
	at org.hibernate.proxy.AbstractLazyInitializer.getImplementation(AbstractLazyInitializer.java:286)
	at org.hibernate.search.hcore.util.impl.HibernateHelper.unproxy(HibernateHelper.java:45)
	at org.hibernate.search.engine.impl.HibernateStatelessInitializer.unproxy(HibernateStatelessInitializer.java:39)
	at org.hibernate.search.engine.spi.DocumentBuilderIndexedEntity.unproxy(DocumentBuilderIndexedEntity.java:795)
	at org.hibernate.search.engine.spi.DocumentBuilderIndexedEntity.buildDocumentFieldsForProperties(DocumentBuilderIndexedEntity.java:605)
	at org.hibernate.search.engine.spi.DocumentBuilderIndexedEntity.buildDocumentFields(DocumentBuilderIndexedEntity.java:463)
	at org.hibernate.search.engine.spi.DocumentBuilderIndexedEntity.buildDocumentFieldsForEmbeddedObjects(DocumentBuilderIndexedEntity.java:533)
	at org.hibernate.search.engine.spi.DocumentBuilderIndexedEntity.buildDocumentFields(DocumentBuilderIndexedEntity.java:479)
	at org.hibernate.search.engine.spi.DocumentBuilderIndexedEntity.getDocument(DocumentBuilderIndexedEntity.java:395)
	at org.hibernate.search.engine.spi.DocumentBuilderIndexedEntity.createUpdateWork(DocumentBuilderIndexedEntity.java:312)
	at org.hibernate.search.engine.spi.DocumentBuilderIndexedEntity.addWorkToQueue(DocumentBuilderIndexedEntity.java:253)
	at org.hibernate.search.engine.impl.WorkPlan$PerEntityWork.enqueueLuceneWork(WorkPlan.java:518)
	at org.hibernate.search.engine.impl.WorkPlan$PerClassWork.enqueueLuceneWork(WorkPlan.java:280)
	at org.hibernate.search.engine.impl.WorkPlan.getPlannedLuceneWork(WorkPlan.java:152)
	at org.hibernate.search.backend.impl.WorkQueue.prepareWorkPlan(WorkQueue.java:114)
	at org.hibernate.search.backend.impl.BatchedQueueingProcessor.prepareWorks(BatchedQueueingProcessor.java:55)
	at org.hibernate.search.backend.impl.PostTransactionWorkQueueSynchronization.beforeCompletion(PostTransactionWorkQueueSynchronization.java:74)
	at org.hibernate.search.backend.impl.EventSourceTransactionContext$DelegateToSynchronizationOnBeforeTx.doBeforeTransactionCompletion(EventSourceTransactionContext.java:174)
	... 75 more

It is not possible to tell from this trace where the root cause is, neither the entity nor the property. Maybe there is a way to improve this as well to at least provide the entity name, id and the property fails during the indexing process?