I'll look at adding a new configuration option org.hibernate.envers.use_numeric_revend_timestamp_field_type for 6.0 that will allow you to influence the use of a long-based data type rather than the default timestamp-based data type for the revision end timestamp field.