The Hibernate Search 4.3 iteration reached its first milestone: version 4.3.0.Alpha1 is now available for download from and Maven repositories.

The theme for the 4.3 development cycle is clustering: we want to make it better, faster and easier to setup multiple nodes using Hibernate Search in both traditional bare-metal clusters and clouds. For now we're focusing on JGroups and Infinispan integrations but other contributions in the area are very welcome.

JGroups backend

Besides some minor bugfixes and improved logging messages, the big news is automatic master election.

Rather than having to setup some jgroupsSlave instances and a single jgroupsMaster instance with different configurations, you can now simply specify jgroups as backend on all your instances and they will elect a single master. The main benefit of this new feature is that when a master fails, it can automatically elect a new one; beware though the failover approach is still experimental and it won't - for one - cleanup stale locks the dead master could have left behind.

### backend configuration = jgroups

Also we introduced some more configuration options for the power user: see the reference documentation for all details.

Updated JBoss modules

The JBoss Modules where updated to match JBoss EAP 6.1 and JBoss AS 7.2 (now renamed WildFly), and now also include the Infinispan Directory for easy usage of Infinispan when deploying in the application server.

The modules are availalble as a zip in Maven repositories, or can be downloaded from; more on how to use it is described in this section of the documentation.

Components upgraded

Many dependencies where upgraded, and integration points are now expecting the following versions:

  • JBoss EAP 6.1
  • Hibernate ORM 4.2.x
  • JGroups 3.2.x
  • Infinispan 5.2.x
  • Lucene 3.6.x (this didn't actually change compared to Hibernate Search 4.2 but it's good to remind the version)

What's next?

In the next few weeks we will be working on better Infinispan integration: easier setup and more configuration examples. Also we have some open tasks about Spatial queries, especially the API needs some polishing.

The complete list of changes can be found on the JIRA release notes.

Links recap:

23. Apr 2013, 10:57 CET | Link

Any work done towards migrating to lucene 4.2? Thats all I care about!

23. Apr 2013, 12:34 CET | Link
Any work done towards migrating to lucene 4.2? Thats all I care about!

Absolutely! But that's a big one as we have a high coupling with the low level Lucene APIs. I'm playing with some experimental branches using latest Lucene, and the lessons learned in there are driving the internal refactoring for 4.3 and 4.4. I didn't advertise these branches as they either don't compile or are not fully functional, we need to revisit some internal components design first.

Both 4.3 and 4.4 will have a quick development cycle with minimal new user visible features, but are mostly about preparing for 5.0 to support Lucene 4.x. It has to be a mayor release as unfortunately some public APIs will have to change to make sense with the new Lucene.