Greetings!  I am having an issue where the audit table being automatically generated through Envers collects unnecessary columns into the primary key and I was hoping for some advice regarding how we might overcome this problem.  In particular, we have multiple data objects that include a "properties" field, which is of type Map<String, String>.  I have copied an example from our hbm2ddl logging output of the main table and audit table created in this case:

create table TICKET_PROPERTIES (TICKET_ID integer not null, PROPERTY_VALUE varchar(255), PROPERTY_KEY varchar(255) not null, primary key (TICKET_ID, PROPERTY_KEY)) ENGINE=InnoDB

create table TICKET_PROPERTIES_AUD (REV integer not null, TICKET_ID integer not null, PROPERTY_VALUE varchar(255) not null, PROPERTY_KEY varchar(255) not null, REVTYPE tinyint, primary key (REV, TICKET_ID, PROPERTY_VALUE, PROPERTY_KEY)) ENGINE=InnoDB

The issue is that Envers includes the property_value in the primary key for the audit table; this causes a problem (specifically, going over the maximum key length) if we want to expand the length of the property_value column.  It is my understanding that the property_value really doesn't need to be in the primary key anyway, since the rev, data_id, and property_key together will be unique.  Is there perhaps some way of telling Envers what information should be included in the audit table's primary key?