Hibernate Search 5.10.0.Beta2 is out!

Posted by    |      

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 5.10.0.Beta2, the second beta release for the 5.10 branch. This release mainly includes an upgrade to WildFly 12 for the JBoss modules, but it also adds a few bugfixes and improvements: see below!

What’s new?

Here are some notable changes since Hibernate Search 5.10.0.Beta1:

  • HSEARCH-3022: Hibernate Search’s JBoss modules now target WildFly 12 and are tested against it instead of WildFly 11.

  • HSEARCH-2598: The JGroups backend now integrates with JGroups 4 and is no longer compatible with JGroups 3.

  • HSEARCH-3030: We moved the JGroups backend’s JBoss modules out of the engine feature pack to a dedicated feature pack.

  • HSEARCH-3026: If your Elasticsearch cluster is accessed through a URL with a non-root path, you can now use hibernate.search.default.elasticsearch.path_prefix to tell Hibernate Search about that path.

  • HSEARCH-3039: We removed the ability to analyze document identifiers from Search a few versions ago, but some parts of Hibernate Search still performed analysis on document identifiers in some cases, in particular when querying them and when embedding a document ID using @IndexedEmbedded. This has been fixed: Hibernate Search now consistently skips analysis on document identifiers.

  • HSEARCH-3021: The integration to dependency injection frameworks is now properly documented.

For a full list of changes since 5.10.0.Beta1, please see the release notes.

Next

We are currently still waiting for Hibernate ORM 5.3.0.Final to be released. You can expect a CR1 of Hibernate Search 5.10 soon after the ORM 5.3.0.Final release.

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