In Relation To

We just published a bugfix release for Hibernate Search: 6.0.5.Final.

Thanks to Lorenzo for his bug report!

We just published a bugfix release for Hibernate Search: 6.0.4.Final.

Thanks to Aaron Kunde for his report!

We just published two maintenance releases for Hibernate Search: 5.11.9.Final and 5.10.11.Final.

The most significant change in these versions is the upgrade to Avro 1.10 and Jackson 2, which should only impact users of clustering features involving Avro serialization.

We just published a bugfix release for Hibernate Search: 6.0.3.Final.

Thanks to Griffin DeJohn, Keith Melkild and Jan Kunzmann for their reports!

We just published a bugfix release for Hibernate Search: 6.0.2.Final.

We just published a bugfix release for Hibernate Search: 6.0.1.Final.

We just published a bugfix release for Hibernate Search: 5.11.8.Final.

We just published the first stable release of Hibernate Search 6: version 6.0.0.Final.

With more than 900 tickets addressed over the course of 20 alphas and betas, Hibernate Search 6 really is a major release, and it shows.

The most obvious changes: an overhauled API better suited to working with Elasticsearch (but that still works perfectly with embedded Lucene), and upgrades from Lucene 5 to 8 and from Elasticsearch 5.6 to 7.

But it doesn’t stop there: a safer and more concise Search DSL, easier mapping, more powerful bridges, smarter automatic indexing, nested documents, …​

We just published a second candidate release for Hibernate Search 6.0: version 6.0.0.CR2.

This release mainly brings a workaround for applications hanging on startup with Spring Boot 2.3+, type parameters for type bridges and property bridges, and an alternative, URI-based configuration for target Elasticsearch hosts.

It also includes an upgrade to Lucene 8.7.0, Elasticsearch 7.10.0 and Hibernate ORM 5.4.24.Final.

We just published two bugfix releases for Hibernate Search: 5.11.7.Final and 5.10.10.Final.

The only significant change in these versions is the upgrade to Hibernate ORM version 5.4.24.Final and 5.3.20.Final, respectively, in order to fix CVE-2020-25638.