We just published Hibernate Search version 5.8.0.CR1, with bugfixes and improvements over 5.8.0.Beta4.
Version 5.8.0.CR1 is the last opportunity for the community to test it and report bugs before the release.
Hibernate Search 5.8.x, just as 5.7.x, is only compatible with Hibernate ORM 5.2.3 and later.
If you need to use Hibernate ORM 5.0.x or 5.1.x, use the older Hibernate Search 5.6.x.
Here are the most notable changes:
HSEARCH-2831: request signing for Amazon’s proprietary IAM authentication mechanism now requires you to set the
true, allowing you to easily disable signing even if the
hibernate-search-elasticsearch-awsJAR is in your classpath.
HSEARCH-2764: we improved the orchestration of index updates before they are sent to the Elasticsearch client:
Index updates originating from a single Hibernate Search node will now be sent to Elasticsearch in the order they were generated, even when they come from different threads.
Mass indexing will now add documents in parallel, allowing you to take advantage of having multiple connections to the Elasticsearch cluster. Note you can customize the maximum number of connections using the
The internal index update queues are now bounded, thus performing mass indexing on very large data sets will not trigger an
We also made several other internal changes to improve performance (less Refresh API calls, more request bulking, …).
HSEARCH-2839: when using a metadata-providing bridge, the bridge can now implement projection on the default field even if its type was set to
HSEARCH-2843: changing the limit/offset of a query now properly clears the query’s result cache with Elasticsearch.
For a full list of changes since 5.8.0.Beta4, please see the release notes.
All versions are available on Hibernate Search’s web site.
Ideally use a tool to fetch it from Maven Central; these are the coordinates:
<dependency> <groupId>org.hibernate</groupId> <artifactId>hibernate-search-orm</artifactId> <version>5.8.0.CR1</version> </dependency>
To use the experimental Elasticsearch integration you’ll also need:
<dependency> <groupId>org.hibernate</groupId> <artifactId>hibernate-search-elasticsearch</artifactId> <version>5.8.0.CR1</version> </dependency>
To use Amazon’s proprietary IAM authentication mechanism to access your Elasticsearch cluster you’ll also need:
<dependency> <groupId>org.hibernate</groupId> <artifactId>hibernate-search-elasticsearch-aws</artifactId> <version>5.8.0.CR1</version> </dependency>
Downloads from Sourceforge are available as well.