In Relation To

Back to home

Hibernate OGM 4.1.0.Beta8 is out: Optimistic locking and performance improvement

Posted by    |      

Hibernate OGM is not maintained anymore

We are getting closer to a final release and this version is mainly about improving general performance and reducing the amount of round trips to the datastore. We also added optimistic locking support for datastores which provide atomic find-and-update operations.

We also worked on several bug fixes and improvements under the hood, you can read more about it in the release note.

Optimistic locking detection

With Hibernate ORM, you can add optimistic locking capability to an entity using the @Version annotation: 



@Entity
public class Flight implements Serializable {
...
    @Version
    @Column(name="OPTLOCK")
    public Integer getVersion() { ... }
} 






So far Hibernate OGM’s support for this was limited to CouchDB, which has its own proprietary optimistic locking mechanism. In this release we added support for optimistic locking also for those datastores that provide atomic find-and-update semantics such as MongoDB.





As always, you can either download a release bundle from SourceForge or get the JARs from the JBoss Nexus
repository server using Maven, Gradle etc. The GAV coordinates are:




    

  •  org.hibernate.ogm:hibernate-ogm-core:4.1.0.Beta8 for the OGM engine and
    • 

  •  org.hibernate.ogm:hibernate-ogm-<datastore>:4.1.0.Beta8, depending on the backend you want to use.
    • 




What's next?





We are currently focused is on improving performance, documentation, polishing the API and fixing last minute bugs.





You're very welcome to raise your voice on the mailing list, ask questions in the forum or report any bugs or feature requests in the issue tracker.























Back to top