Hibernate Search is a library that integrates Hibernate ORM with Apache Lucene or Elasticsearch by automatically indexing entities, enabling advanced search functionality: full-text, geospatial, aggregations and more. For more information, see Hibernate Search on hibernate.org.

We just published Hibernate Search 6.0.0.Alpha8, a new release of the still-in-development 6.0 branch. This release mainly restores configuration options for entity loading and Lucene index storage, brings simpler and more powerful bridge APIs, and upgrades to Elasticsearch 7.2 and Lucene 8.1.

Getting started with Hibernate Search 6

If you want to dive right into the new, shiny Hibernate Search 6, a good starting point is the getting started guide included in the reference documentation.

Hibernate Search 6 is still in development and its APIs differ significantly from Search 5.

For more information about the current status of this branch, see the page dedicated to Search 6 on hibernate.org.

For more information about migration and what we intend to do to help you, see the migration guide.

What’s new

Configurable, tested and optimized entity loading

As of HSEARCH-3349, entity loading has been optimized, tested more thoroughly, and is now configurable.

Head to this section of the documentation for more information about configuration options.

Configurable and extensible Lucene storage

As of HSEARCH-3440, Lucene index storage can now be configured more finely, and if you’re an integrator, you can even plug in your own storage technology.

Head to this section of the documentation for more information about configuration options.

Simpler and more powerful bridge APIs

As of HSEARCH-3609, the new bridge APIs have been polished to be simpler to use for simple cases, and safer yet powerful for more complex use cases.

For an early look at these APIs, head over to this pull request. More in-depth explanations will be added to the documentation in the next few releases.

Backward-incompatible API changes

As of HSEARCH-3602, DSL interface now use the "Step" suffix instead of the "Context" suffix. This generally should not impact existing client code, as these interfaces are not meant to be used directly (you don’t need to declare variables with these types).

Some types have also been renamed for consistency, and these renamings will impact existing code: in particular, the type of the "context" parameter in *Configurer types has changed.

HSEARCH-3609 also brought backward-incompatible changes to the bridge APIs, which are not yet documented.


The documentation was restored for the following features:

Version upgrades

Other improvements and bug fixes

  • HSEARCH-3607: @GenericField can now be used on properties of type GeoPoint.

  • HSEARCH-3641: It is now possible to define a native Elasticsearch field with a type that is not supported directly by Hibernate Search. Thanks to Alexis Cucumel for reporting this!

And more. For a full list of changes since the previous releases, please see the release notes.

How to get this release

All details are available and up to date on the dedicated page on hibernate.org.

Feedback, issues, ideas?

To get in touch, use the following channels:

Back to top