Seems EnversRevisionRepositoryImpl.findRevision(ID id, N revisionNumber) behavior has changed: entity must now exist at revisionNumber, not only in a previous revision

[cguillot]

Hello,

I am upgrading to spring-data envers 2.3.2 (from 2.2.4) and i am facing an issue due to changes in the implementation of EnversRevisionRepositoryImpl.findRevision.

Quick scenario:
Create an entity type A, save it. Entity A.1 created at revision 1.
Create an entity type B, save it. Entity B.1 created at revision 2.
Now envers higher revision is 2.

Then, we want to retrieve entity A.1 at last known revision (2):

Result in 2.3.2
findRevision(A.1, 2) return nothing.

Result in 2.2.4
findRevision(A.1, 2) return A.1

My Expectations
I would expect the entity A.1 at revision 1 to be also the revision 2.