Inspired by these questions on the Search forum and stackoverflow I decided
to blog about different solutions for the problem using only the tools available in Search right now (4.1.1.Final). But let's start with the problem.
A bugfix release for Hibernate Search 4.1 ! Some of you have been reporting reduced performance after migrating from 3.4 or 4.0, which was not expected at all as the internals got smarter at each release. It turns out there was a quite critical bug: file handle leaks.
Another CR for Hibernate Search 4.1 is ready! Even being in candidate release phase, we introduced something more than the usual minor bugfixes, as the following improvements are too nice to delay and technically not very risky.
We have decided to do a second release candidate for Hibernate Search 4.1. We fixed a couple of issues related to
clustering and how it works in a modular environment like JBoss AS 7. In particular, we made sure it works fine for JBoss AS 7.1.
This release will hopefully be the last before Hibernate Search 4.1 final. If you want to give feedback,
now is the time :) We are simultaneously releasing Hibernate Search 3.4.2 as a minor bug fix release.
Hibernate Search version 4.1.0.Beta1 was tagged; the most essential change compared to January's release 4.1.0.Alpha1 was HSEARCH-1034, made to allow Infinispan Query to use the fluent Programmatic Mapping API as already available to Hibernate users.