We just published Hibernate Search 6.0.0.Beta3. This release mainly brings schema improvements, deep customization of Elasticsearch search requests, more powerful bridge definitions, and restores features such as the search query timeouts. It also includes upgrades to Lucene 8.3.0, Elasticsearch 7.5 and Hibernate ORM 5.4.10.Final.
Today, we published a new maintenance release of Hibernate ORM 5.4: 5.4.10.Final.
We are excited to announce the release of 6.0 Alpha3.
The main design goal for 6.0 is to improve even more Hibernate’s through-put performance. High-load performance
testing showed that Hibernate’s approach of reading values from
ResultSet by name to be its most limiting factor in
scaling through-put. At its most basic, 6.0 is all about changing from its old strategy of read-by-name to
read-by-position. But that simple goal has a lot of ramifications.
We have come really far, but still it is an Alpha, so there is still plenty more to do.
We just published two bugfix releases for Hibernate Search: 5.11.4.Final and 5.10.8.Final. These releases mainly upgrade Hibernate Search to the latest compatible Hibernate ORM versions and fix one issue with the Elasticsearch integration.
This blog post is long overdue but here comes the proper announcement of Hibernate Validator 6.1.0.Final and 6.0.18.Final.
Hibernate Validator 6.0.18.Final includes only bugfixes. It is a recommended upgrade for everyone using Hibernate Validator and it is a drop-in replacement for 6.0.17.Final.
6.1.0.Final is our latest and greatest. It is based on Jakarta Bean Validation. More on that one in a bit.
First thing, to clarify, we’re talking about “Hibernate ORM with Panache”, which roughly means we’re talking about a flamboyant and reckless flavour of Hibernate ORM.
This means two essential things:
It’s the full Hibernate ORM, not anything less
But it looks different to what you’re used to
You can fallback at any time and even mix vanilla JPA and Panache
Today, we published a new maintenance release of Hibernate ORM 5.4: 5.4.9.Final.
Hibernate libraries can be used with many frameworks, and we’re striving to make sure that everyone gets their fair share of Hibernate goodness. So with the recent announcement of the first release candidate of Quarkus, the "supersonic, subatomic" Java stack, it’s worth mentioning that Hibernate ORM, Search and Validator are already included in Quarkus.
Hibernate Search in particular, the library adding the power of full-text search to your ORM-based application, is included in its most recent version (6.0.0.Beta2), which adds first-class compatibility with Elasticsearch.
Let’s take this Quarkus release as an opportunity to have a closer look at Hibernate Search 6, and how it can be used in Quarkus.
Today, we released a new maintenance release of Hibernate ORM 5.3: 5.3.14.Final.
We just published Hibernate Search 6.0.0.Beta2. This release mainly introduces search analyzers, improves background failure handling and upgrades to Elasticsearch 7.4 and Hibernate ORM 5.4.7.Final.