For a long running transactions that e.g. insert lots of new entities AuditProcess keeps growing until the transaction is committed - it's the first moment when Envers actually flushes the audit write operations to DB. The behavior doesn't change even if we manually flush/clear the hibernate session - the session gets clear but AuditProcess stays as it was before.

It would be great to have an entrypoint (public API) in AuditProcess that allows users to actually perform manual flushes, whenever they decide to do so.