Hibernate Search

5.10 series stable

ORM 5.3 and JPA 2.2 compatibility, integration to DI frameworks through Hibernate ORM 5.3, upgrade to WildFly 17 and JGroups 4, JPMS automatic module names.


Java 8 or 11 (with 5.10.7+)
Hibernate ORM 5.3
Elasticsearch 2.0 - 5.6
Apache Lucene 5.5

Not compatible with your requirements? Have a look at the other series.

See also the Compatibility policy.


Documentation for this specific series can be accessed through the links below:


You can find more documentation for all series on the documentation page.

How to get it

Maven, Gradle...

Maven artifacts of Hibernate Search are published to Maven Central and to the JBoss Maven repository. Refer to the Maven Getting Started guide on the JBoss Wiki for more information on how to configure the JBoss Maven repository.

You can find the Maven coordinates of all artifacts through the link below:

Maven artifacts

Below are the Maven coordinates of the main artifacts.

Hibernate ORM integration
Elasticsearch integration
Amazon IAM authentication for Elasticsearch
JGroups backend
JMS backend
JSR 352 (Batch for Java) integration - Core
JSR 352 (Batch for Java) integration - JBeret specifics
WildFly feature pack - Engine
WildFly feature pack - Hibernate ORM integration
WildFly feature pack - Elasticsearch integration
WildFly feature pack - Amazon IAM authentication for Elasticsearch
WildFly feature pack - JGroups backend

Zip archive

Direct download is available from SourceForge:

Download Zip archive

More information about specific releases (announcements, download links) can be found here.


If you need to upgrade from a previous series, please refer to the migration guide:


What's new

Latest release announcement (2020-11-18): 5.10.10.Final.

A detailed list of new features, improvements and fixes in this series can be found on our JIRA instance.

ORM 5.3 and JPA 2.2 compatibility

Hibernate Search 5.10 is designed to work with Hibernate ORM 5.3.

Integration to DI frameworks through Hibernate ORM 5.3

Hibernate Search now taps into Hibernate ORM’s integration to dependency injection frameworks. If you use a dependency injection framework integrating with Hibernate ORM 5.3, and you add field bridges to your dependency injection context, then Hibernate Search will automatically retrieve and use field bridges from this context.

This allows you in particular to inject components from your DI context into your field bridges, using your DI framework’s features (@java.inject.Inject, Spring’s @Autowired, …​).

The integration is known to work in a CDI 2.0 environment such as WildFly 17, and also in Spring 5.

Upgrade to WildFly 17 and JGroups 4

Hibernate Search’s JBoss modules now target WildFly 17. This means in particular that the JGroups backend now uses JGroups 4 and is no longer compatible with JGroups 3.

Also, we took this opportunity to move the JGroups backend’s JBoss modules out of the engine feature pack to a dedicated feature pack.

JPMS automatic module names

We added automatic JPMS module names to our JARs.

Note that Hibernate Search JARs still can only be used as automatic modules, because some of our dependencies cannot easily be used as modules yet.

Here are the module names:

  • org.hibernate.search.engine

  • org.hibernate.search.orm

  • org.hibernate.search.backend.elasticsearch

  • org.hibernate.search.backend.elasticsearch.aws

  • org.hibernate.search.clustering.jms

  • org.hibernate.search.clustering.jgroups

  • org.hibernate.search.jsr352.core

  • org.hibernate.search.jsr352.jberet

  • org.hibernate.search.serialization.avro

Direct access to the Elasticsearch client

Hibernate Search now offers a way to access the Elasticsearch client directly. See the documentation for more information.

Releases in this series





Back to top