In Relation To

We just published Hibernate Search 7.2.0.Alpha1, the first alpha release of the next minor version of Hibernate Search.

This version contains many improvements to the Search DSL, including new projection types, predicate improvements, query parameters and more.

It also upgrades Lucene and Hibernate ORM dependencies and includes compatibility with the latest OpenSearch 2.14.

We are pleased to announce the releases of Hibernate Search 7.1.1.Final, 7.0.1.Final and 6.2.4.Final.

While these releases are mainly to address some minor documentation discrepancies, they also bring compatibility with newer versions of Elasticsearch and OpenSearch and a few bugfixes.

We are pleased to announce the release of Hibernate Search 7.1.0.Final.

Compared to Hibernate Search 7.0, this release introduces vector search capabilities, allows looking up the capabilities of each field in the metamodel, adds a new query string predicate, simplifies the entity registration in the Standalone POJO mapper, brings compatibility with Elasticsearch 8.12 and OpenSearch 2.12, upgrades to Lucene 9.9, and brings other bugfixes and improvements.

We just published Hibernate Search 7.1.0.CR1, a first candidate release of the next minor version of Hibernate Search.

This version brings a lot of updates and improvements for working with a Standalone POJO mapper, new query string predicate, and takes advantage of Elasticsearch 8.12 to remove some of the limitations on vector search capabilities.

We just published Hibernate Search 7.1.0.Alpha2, a second alpha release of the next minor version of Hibernate Search.

This version brings more vector search capabilities and improvements as well as integrates Elasticsearch’s/OpenSearch’s vector search capabilities.

We just published Hibernate Search 7.1.0.Alpha1, a first alpha release of the next major version of Hibernate Search.

This version opens up possibilities for searching over binary (image, audio or video) data using vector search.

Beyond that, it improves Hibernate Search compatibility with other frameworks.

We just published Hibernate Search 7.0.0.Beta1, a first beta release of the next major version of Hibernate Search.

The main theme of this new major version is upgrades: JDK 11 as a baseline, switch to Jakarta EE and to the latest Hibernate ORM, upgrade of the Lucene backend to the next major version (Lucene 9).

Beyond that, 7.0.0.Beta1 also includes experimental compatibility with Amazon OpenSearch Serverless, publishes a Hibernate Search BOM containing all of its public artifacts, and more.

We used to be very conservative on the constraints included in Hibernate Validator but we changed this policy recently and we would like to have more constraints built-in.

Of course, we won’t accept everything: the proposed constraints needs to be of general usage and well defined but the idea is to have more features in Hibernate Validator out of the box.

This post will be useful to those who have some interesting custom Bean Validation constraints and want to share them with the community.

Today we’ll be talking about Hibernate Validator and how you can provide your own constraints and/or validators in a fully self-contained manner. Meaning packaging it all into its own JAR file, in a way that others can use your library by simply adding it to the classpath.

This functionality is based on Hibernate Validator usage of Java’s ServiceLoader mechanism that allows to register additional constraint definitions. But more on the details later.

What can be a real life scenario for building your own library with constraints and sharing it? Well, let’s say that you are building some library with data classes that user might want to validate. As it may be tough to keep track of all such libraries and write/maintain all those constraints for them - Hibernate Validator provides authors of such libraries a possibility to write and share their own validation extensions. Which can be picked up by Hibernate Validator and used to validate your data classes.