While the team has been busy implementing great new features such as the Elasticsearch integration for the next 5.6 release, some of you provided interesting feedback on our stable release.
The summary of the feedback I heard is that migrating to the new sorting requirements can be confusing, and there were some issues with our Faceting implementation.
Hibernate Search version
5.5.3.Final is available now, fixing the reported issues and improving the error messages around sorting.
The changelog is rather small, so this time I’ll post it verbatim:
HSEARCH-1917 - Cannot index null or empty values for faceted fields
HSEARCH-2082 - Documentation refers to @SortField when it should be @SortableField
HSEARCH-2085 - Typo in hibernate-search-engine logger
HSEARCH-2086 - Long and Date range faceting doesn’t honor hasZeroCountsIncluded
HSEARCH-2179 - Hanging during shutdown of SyncWorkProcessor
HSEARCH-2193 - LuceneBackendQueueTask does not release the Directory lock on update failures
HSEARCH-2200 - Typo in log message
HSEARCH-2240 - Parallel service lookup might fail to find the service
HSEARCH-2199 - Allows the use of CharFilter in the programmatic API of SearchMapping
HSEARCH-2084 - Upgrade to WildFly 10.0.0.Final
HSEARCH-2089 - Ensure the performance tests do not use the WildFly embedded version of Search
HSEARCH-1951 - Improve resulting error message when applying the wrong Sort Type
HSEARCH-2090 - Using the wrong header in the distribution/pom.xml
HSEARCH-2241 - Clarify deprecation of setFilter() method on FullTextQuery
We are getting closer and closer to the final release of Hibernate OGM 5.
This release includes support for Redis Cluster and
a new dialect to store data within Redis hashes;
java.util.UUID are now
using the native
uuid type in Apache Cassandra;
more queries are now supported using the MongoDB CLI syntax.
The migration notes contains more information about migrating from earlier versions of Hibernate OGM to 5.x.
Have a look at the change log for a list of everything included in this release.
Having fixed several issues and tasks since the previous milestone, it’s time to publish our third milestone towards Elasticsearch integration: Hibernate Search version 5.6.0.Alpha3 is now available!
Today we’re proud to announce the first Alpha release sporting experimental integration with Elasticsearch!
We also updated to use Apache Lucene 5.5 - the latest stable release of our favourite search engine - as of course we’re not abandoning our traditional users!
It’s my pleasure to announce the release of Hibernate Validator 5.2.4.Final!
This is a rather small bugfix release which addresses two nasty issues around one of the more advanced features of Bean Validation, redefined default group sequences.
The Hibernate team is proud to announce the release of ORM 5.1 which includes a number of new features and enhancements, including:
It’s my pleasure to announce the release of Hibernate Validator 5.2.3.Final!
Wait, didn’t we already do another Hibernate Validator release earlier this month? That’s right, indeed we pushed out the first Alpha of the 5.3 family a couple of days ago. And normally, that’d mean that there would be no further releases of earlier version families.
But in this case we decided to do an exception from the rule as we noticed that Hibernate Validator couldn’t be used with Java 9 (check out issue HV-1048 if you are interested in the details). As we don’t want to keep integrators and users of Hibernate Validator from testing their own software on Java 9, we decided to fix that issue on the current stable release line (in fact we strongly encourage you to test your applications on Java 9 to learn as early as possible about any potential changes you might need to make).
It’s my pleasure to announce the first release of Hibernate Validator 5.3!
The overarching idea for the 5.3 timeline is to prototype several features which may potentially be standardized in the Bean Validation 2.0 specification. For instance we’ll work on a solution for the long-standing request for sorting the constraints on single properties.
If you’d like to see any specific features addressed in that prototyping work (and eventually included in BV 2.0), then please get in touch and let us know which are the most important things you are missing from the spec. We’ve compiled a first list of issues we are considering for inclusion in BV 2.0. For sure we cannot address all of them, so it’ll greatly help if you tell us what would be most helpful to you.