In Relation To

We just published the first candidate release for Hibernate Search 6.0: version 6.0.0.CR1.

Compared to Hibernate Search 5, changes are extensive, due to the API overhaul, but with plenty of improvements: upgrades to Lucene 8 and Elasticsearch 7 of course, but also a more concise Search DSL with typed result types, full control on field declaration in Bridges, easier to configure and more efficient automatic indexing, runtime joins with nested documents, …​

No more changes are planned before the final release, so this is the perfect time to test your applications based on Hibernate Search, and report problems as soon as possible so that everything works perfectly as soon as 6.0.0.Final is released.

Version 5.4.23.Final of Hibernate ORM is available now: allow me to highlight some fixes and enhancements.

We just published Hibernate Search 6.0.0.Beta11.

This release mainly brings a default analyzer, a way to limit automatic reindexing to same-entity updates only, a new implementation for AWS IAM authentication, and a migration helper for applications moving from Search 5 to Search 6.

It also includes an upgrade to Lucene 8.6.2, and Hibernate ORM 5.4.22.Final.

Last night we released Hibernate ORM version 5.4.22.Final.

This is a micro release: the result of backporting a number of fixes to our stable branch.

We just released Hibernate Validator 6.1.6.Final which contains a few fixes and the new @Normalized constraint.

This is a recommended upgrade for everyone using Hibernate Validator and it is a drop-in replacement for 6.1.5.Final.

We also released 6.0.21.Final.

We just published Hibernate Search 6.0.0.Beta10.

This release mainly brings a total hit count threshold, conditional indexing, better timeouts, and per-index analyzer definitions for Elasticsearch.

It also includes an upgrade to Lucene 8.6.1, Elasticsearch 7.9.0 and Hibernate ORM 5.4.21.Final.

Today, we published a new maintenance release of Hibernate ORM 5.4: 5.4.21.Final.

Hibernate ORM 6.0 Alpha6 has just been released.

The main design goal for 6.0 is to improve even more Hibernate’s through-put performance. High-load performance testing showed Hibernate’s approach of reading values from ResultSet by name to be its most limiting factor in scaling throughput. 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.

This Alpha6 release includes:

A new Hibernate ORM release is available: 5.4.20.Final is a micro release, resolving some minor annoyances and to help our experimentation with Hibernate Reactive.

Today, we published a new maintenance release of Hibernate ORM 5.3: 5.3.18.Final.