Default map key column renamed to <field>_KEY
For Map-valued fields without @MapKeyColumn the key column was previously named KEY (which most dictionaries turned into KEY0 because KEY is a reserved word). As required by section 11.1.35 of the specification, the default is now the field name followed by \_KEY (for example PHONES_KEY). Schemas created by earlier releases no longer match: schema validation fails, SynchronizeMappings=buildSchema adds a new column and existing key data reads back as null.
Declare the existing column explicitly, for example @MapKeyColumn(name="KEY0"), or rename the column in the database.
Alternatively, set the openjpa.Compatibility option UseSpecDefaultMapKeyColumnName to false, which restores the old default for all map fields that do not declare a key column:
<property name="openjpa.Compatibility" value="UseSpecDefaultMapKeyColumnName=false"/>
An explicit @MapKeyColumn is honoured regardless of the setting.
See also Map Mapping.