5.2 series - Hibernate OGM

Quick links

Compatibility

Not compatible with your requirements? Have a look at the other series.

Documentation for this specific series can be accessed through the links below:

You can find more documentation for all series on the documentation page.

Maven artifacts of Hibernate OGM are published to Maven Central and to the JBoss Maven repository. Refer to the Maven Getting Started guide on the JBoss Wiki for more information on how to configure the JBoss Maven repository.

You can find the Maven coordinates of all artifacts through the link below:

Below are the Maven coordinates of the main artifacts.

org.hibernate.ogm:hibernate-ogm-infinispan-embedded:5.2.0.Final: Infinispan integration (embedded)
org.hibernate.ogm:hibernate-ogm-infinispan-remote:5.2.0.Final: Infinispan integration (remote)
org.hibernate.ogm:hibernate-ogm-mongodb:5.2.0.Final: MongoDB integration
org.hibernate.ogm:hibernate-ogm-neo4j:5.2.0.Final: Neo4j integration

Direct download is available from SourceForge:

More information about specific releases (announcements, download links) can be found here.

Latest release announcement (2018-02-05): 5.2.0.Final.

A detailed list of new features, improvements and fixes in this series can be found on our JIRA instance.

We have split the dialects in 2:

the ones maintained in the main repository: Infinispan, MongoDB, Neo4j
the ones maintained by the community which have been moved to separate repositories: Cassandra, CouchDB, EhCache, Apache Ignite and Redis

OGM now requires Java 8 or later.

Upgrade to Infinispan 9.1
Automatically create caches when needed with Infinispan Remote via Hot Rod
Use Infinispan Clustered Counters for sequences and id generation with Infinispan Embedded
Operation grouping: OGM automatically groups write operations when it is possible.

We upgraded to the MongoDB 3 API
Use MongoDB Driver version 3.6
Support GeoSpatial data type
Support distinct operations in native queries
Support Map/Reduce operations in native queries
Remove Fongo dialect as it wasn’t really useful and it generated some maintenance burden