|Elasticsearch||2.0 - 5.6|
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
More information about specific releases (announcements, download links) can be found here.
Latest release announcement (2018-05-17): 5.10.0.Final.
A detailed list of new features, improvements and fixes in this series can be found on our JIRA instance.
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 (
The integration is already known to work in a CDI 2.0 environment such as WildFly 12, and the Spring team will probably make it work as soon as it adds support for JPA 2.2.
Hibernate Search’s JBoss modules now target WildFly 12. 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.
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:
Hibernate Search now offers a way to access the Elasticsearch client directly. See the documentation for more information.
If you need to upgrade from a previous series, please refer to the migration guide.
Releases in this series