I use envers with the validity audit strategy where the end revision is stored for fast lookups. Additionally, I store the end revision timestamp for an useful partitioning scheme as described in the envers user guide.
The problem is, that the end revision timestamp is not stored in tables which are used by entities which are mapped with the joined-subclass mapping strategy. Of course, the end revision must not be stored in such tables, because they are joined with the superclass table where the end revision is stored. However, the end revision timestamp is necessary for partitioning.