[hibernate-issues] [Hibernate-JIRA] Created: (HHH-6592) Problem with the Envers revision numbering for multi-node applications

[Oleksandr Alesinskyy (JIRA)]

Problem with the Envers revision numbering for multi-node applications
----------------------------------------------------------------------

                 Key: HHH-6592
                 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6592
             Project: Hibernate Core
          Issue Type: Improvement
            Reporter: Oleksandr Alesinskyy
            Priority: Critical


There is a problem with the revision numbering performed by Envers if an application is executed on the several nodes, namely:
you either have to define a strictly serial ID generator for the Revision Entity such drastically impact a performance of all CRUD operations involving audited entities or forRevisionsOfEntity becomes broken, as it may occurs that a parent entity contains a child entity which was firstly created with the revisions higher then the last revision of the parent entity (as this "newer" revision has timestamp that predates a timestamp .of the "older" revision - and this may be not milliseconds but minutes).

>From my point of view  queries used by Envers shall take into account not so much revision numbers, as timestamps (at least as an alternative configurable mode).


--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira