Hibernate Search

5.10 series development

ORM 5.3 and JPA 2.2 compatibility


Java 8+
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.


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

Zip archive

Direct download is available from SourceForge:

Download Zip archive

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

What's new

Latest release announcement (2018-02-22): 5.10.0.Beta1.

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.injext.Inject, Spring’s @Autowired, …​).

The integration is already known to work in a CDI 2.0 environment such as WildFly 12 (not released yet as of February 23, 2018), and the Spring team will probably make it work as soon as it adds support for JPA 2.2.

Releases in this series

Back to top