We just published 5.9.0.Beta1, the first beta release for the 5.9 branch. This release brings several bug fixes, but most importantly a new mass indexer based on the JSR 352 specification, "Batch Applications for the Java Platform"!
What’s new?
Here are the most notable changes since Hibernate Search 5.8.0.Final:
-
HSEARCH-2594: A JSR 352 mass indexing job was added, adding in particular the ability to restart from a checkpoint when indexing fails. We will soon post a blog post with more information about how it is better than the original mass indexer and how to use it, so stay tuned!
-
HSEARCH-2832: Exception messages when an Elasticsearch work fails are now a bit less verbose. In particular they don’t include the failing request anymore, because it can often be huge and ends up flooding the logs (especially due to request bulking). You can still log every Elasticsearch request as explained in the documentation.
-
HSEARCH-2883: Requests to Elasticsearch clusters with URL-based access control used to fail because of a trailing slash. This is no longer the case.
-
HSEARCH-2886: In certain circumstances, Elasticsearch requests containing 3 or 4-byte unicode characters could fail. These encoding issues have been resolved.
-
HSEARCH-2909: Annotations in the default package will no longer make the annotation processing fail.
-
HSEARCH-2935: The CPU cost of static initialization of Hibernate Search loggers has been sensibly reduced, improving startup performance.
For a full list of changes since 5.8.0.Final, please see the release notes.
How to get this release
All the necessary information is available (and updated regularly) on hibernate.org.
Feedback, issues, ideas?
To get in touch, use the following channels:
-
hibernate-search tag on Stackoverflow (usage questions)
-
User forum (usage questions, general feedback)
-
Issue tracker (bug reports, feature requests)
-
Mailing list (development-related discussions)
