Tags
Authors
It’s my pleasure to announce the first Alpha release of Hibernate OGM 5!
This release is based on Hibernate ORM 5.0 Final which we released just last week.
The update should be smooth in general, but you should be prepared for some changes if you are bootstrapping Hibernate OGM manually through the Hibernate API and not via JPA.
If you are using Hibernate OGM on WildFly, you need to adapt your application to the changed module/slot name of the Hibernate OGM core module which has changed from org.hibernate:ogm to org.hibernate.ogm:main.
Check out the Hibernate OGM migration notes to learn more about migrating from earlier versions of Hibernate OGM to 5.x. Also the Hibernate ORM migration guide is a recommended read.
Today I have released Hibernate ORM 5.0 (5.0.0.Final). This has been a long time coming and is the result of the efforts of many folks. Thanks to everyone who helped us get here with fixes, bug reports, suggestions, input and encouragement!
A lot of development has gone into 5.0. Here are the big points:
In the last couple of months we’ve been working to upgrade Hibernate Search to use Apache Lucene 5,
to keep up with the greatest releases from the Lucene community.
Today Hibernate Search 5.5.0.Alpha1 is available!
As the version suggests this is the first cut, but we’ll also need your feedback and suggestions to better assess the needed steps to evolve this into a great, efficient and stable Final release.
Hibernate ORM 4.2.20.Final was released 24-July-2015. At the time it was released, SourceForge was out of commission so distributions could not be uploaded. I decided to delay the announcement until SourceForge was back in commission and I was able to release 4.3.11.Final on 5-Aug-2015.
Today I released a fourth candidate release for Hibernate ORM 5.0 (5.0.0.CR4). The purpose was entirely to change the defaults for some settings. This allowed some additional fixes and additional documentation work to make it in.
While Hibernate ORM applies some more polish before releasing the final version, so did the Hibernate Search team.
Hibernate Search version 5.4.0.CR2 is now available!
It was built and tested with Hibernate ORM 5.0.0.CR3, again we’re just waiting for that to be final but decided
to release another Candidate Release as some fixes and improvements were recently applied.
Yesterday I released the third candidate release for Hibernate ORM 5.0 (5.0.0.CR3). We felt another CR was warranted because we had some minor integration (SPI) work that we needed to make in to Final, but too much development had happened since the second CR to be considered risk free to just include everything into Final. At any rate CR3 got lots of great TLC :) The complete set of changes can be seen in the Jira changelog. The main changes include:
I know you have been waiting in anticipation, but now it is available - Hibernate Validator 5.2.1.Final :-). Given that it is a drop-in replacement for all 5.x releases, there is no reason to delay an upgrade. Just go and get it.
For the more cautious, here again the highlights of the 5.2 release with pointers to more information.
Writing queries using complex types can be a bit surprising in Hibernate Search. For these multi-fields types, the key is to target each individual field in the query. Let’s discuss how this works.
The other day I came across an interesting mapping challenge which I thought may be worth sharing. If you are a seasoned JPA user, it will probably be nothing new to you, but those not as experienced may find it helpful :)
TL;DR - JPA let’s you override database columns for embedded objects but also for collections of embedded objects; @AttributeOverride and @AssocationOverride can be used for that.
Let’s assume the following entity model representing a person and their home and business address:
[ ... ]
