We would like to inform you about an issue we found in ADAM 5.7 that might impact your environment.
If you make use of the unique identifier feature, which was introduced in ADAM 5.7, you are impacted by this bug:
When you delete a record containing a unique identifier you run the risk of removing other unique identifiers from the cache (up to a maximum of 10). This in turn means that those potentially removed elements are no longer loadable and duplication checks on them will not function properly.
Determine which 10 could be potentially removed, is not possible.
If you do not use the unique identifier feature, there is no issue with using ADAM 5.7.
But if you do, we strongly recommend to wait for 5.7.1 for further development and testing. In case you have this functionality in production or you are in the process of taking this into production, please contact our ADAM Support team (firstname.lastname@example.org) so we can help you decide on the best immediate approach, based on your situation.
We are with highest priority working on a service pack that will fix this. We will keep you informed about the release of it.