Issues
- Index optimisation should commit to publish the performed optimisationHSEARCH-1681Resolved issue: HSEARCH-1681Davide D'Alto
- AbstractJMSHibernateSearchController should handle RuntimeExceptionsHSEARCH-1669Resolved issue: HSEARCH-1669
- Race condition in DirectoryProviderHelper.initializeIndexIfNeeded leads to failure in concurrent bootstrapHSEARCH-1665Resolved issue: HSEARCH-1665Sanne Grinovero
- Packages not exported from osgi bundlesHSEARCH-1663Resolved issue: HSEARCH-1663Gunnar Morling
- Expose configuration to enable Lucene InfostreamHSEARCH-1658Resolved issue: HSEARCH-1658Gustavo Fernandes
- Avro's ConcurrentServiceTest fails occasionallyHSEARCH-1655Resolved issue: HSEARCH-1655Sanne Grinovero
6 of 6
As discussed on the forums, if the IndexWriter isn't committed, even newly opened IndexReaders won't benefit from the optimisation until the first commit happens.
https://forum.hibernate.org/viewtopic.php?f=9&t=1036666
The solution is easy, but this requires a proper integration test.