Over time, an application can accumulate many historical audits and revisions. While these can be deleted either directly in the database or using native SQL queries in Hibernate/JPA, it would be nice if there was a more orderly way to delete history through the Envers query API. Unlike native queries this deletion API wouldn't expose the application to Envers configuration (e.g. raw table names).