We just published Hibernate Search 6.0.0.Beta4.
This release mainly fixes a performance regression in the Lucene backend and introduces an API for plugging in custom behavior on failures during mass indexing.
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 APIs differ significantly from Search 5.
For more information about migration and what we intend to do to help you, see the migration guide.
A performance regression was introduced in version 6.0.0.Beta3 that would slow down search queries performed on large indexes. This was fixed in HSEARCH-3797.
Performance for projections on nested fields was also improved as part of HSEARCH-3786.
As of HSEARCH-3729,
the mass indexer allows customizing the behavior on failure through
in the MassIndexer documentation.
No version upgrades this time.
Hibernate Search 6 requires ORM 5.4.4.Final or later to work correctly. Earlier 5.4.x versions will not work correctly.
HSEARCH-3629: Search query loading options (cache lookup, fetch size, …) are now passed through a dedicated
loading(…)method accepting a lambda expression. See this section of the documentation for more information. The previous syntax still works, but has been deprecated and will be removed soon.
optimizeindex operation has been renamed to
mergeSegmentsthroughout the API. Also, by default, index segments will no longer be merged after mass indexing. This can still be enabled explicitly through massIndexer.mergeSegments For more information about this operation, see this section of the documentation.
All details are available and up to date on the dedicated page on hibernate.org.