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.
It’s 3 days from Christmas and as a present we decided to release the first Beta of Hibernate OGM 5!
The major news in this release is the mapping support for Cassandra 2.2 new data types,
proper handling of the @Lob annotation, post-load event support
and Infinispan 8.
This release also continue the process of aligning Hibernate OGM to the Hibernate 5 family.
After the passage to Hibernate ORM 5 in the previous release, we updated Hibernate Search
to the 5.5 version that also includes the power of Apache Lucene 5.
In the previous
release post we described the improvements about storing map-typed properties on MongoDB and Redis.
We have now applied the same natural mapping on CouchDB.
Check out the Hibernate OGM migration notes
to learn more about migrating from earlier versions of Hibernate OGM to 5.x.
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.
When creating a bug report for any project within the Hibernate family, it’s extremely helpful (and, frankly, required)
to have an adequate test case available. This is obviously important to make reproducing the issue as easy as possible.
But it’s also vital longer-term. Nearly every bug fix should include a regression test, which is frequently based on the
original reproducer (sometimes, it’s the reproducer, verbatim).
To help create useful test cases, we’re opening up a repo with various templates. Please see the READMEs in each
project’s subdir for more info: Hibernate Test Case Templates
As a starting point, the repo contains two templates for ORM:
One of the fundamental principles of Hibernate/JPA is that any writes done through the Session/EntityManager APIs are collected in the persistence context and are only written to the database upon transaction commit. If needed, you can enforce the flushing of changes by explicitly invoking the flush() method. Also Hibernate may trigger a flush automatically, e.g. prior to executing a query. This strategy allows to perform many optimizations, e.g. only persisting the final state of an entity changed several times, make use of batched inserts and others.