Status: Closed (View Workflow)
Affects Version/s: None
Fix Version/s: None
Mapping failures due to "dirty"/"bad" data in the source record aren't handled very gracefully. The exception is AFACT uncaught, resulting in the client to wait indefinitely, or until the request times out.
It would be helpful if an error response was returned to the client, and to log an error message indicating which record was problematic.
Currently this what we get in the log when this happens:
I've seen this caused by non-utf-8 characters in the source record. For example:
"Orcadvm et Schetlandiæ Insularvm accuratissima descriptio"
- An error message is logged indicating that there was a problem mapping the source record to the desired format, including the id of the problematic record.
- Mapping exceptions are caught and handled.
- An error response is returned to the client