Our xDM instance includes a Google Maps API enricher for addresses. We have a couple of records that are written in Chinese characters. These records cause the API to return a 400, which suspends the job.
Is there some way to have the job otherwise succeed and just have those two records fail? Or is it intentional that the entire job fails if any record cannot be enriched?
Best Answer
A
Alexia SIMOND
said
about 2 hours ago
Hello Danny,
If one of the records included in a batch is leading to an error suspending the certification, then the process is stopped for the whole batch.
There is no way to let the certification know to bypass those 2 records and to continue the process for all others.
Hence why, I would advise instead to try and dig as much as possible on why those 2 records are suspending the job.
If you already tried everything in that regard, maybe you could play with the enricher filter to not include those records in the enricher scope in the first place.
Or implement a new validation that would reject those records if you want to handle them manually.
In the meantime, if you don't want this suspension to block the integration queue, you can deactivate the option "suspend on error":
If one of the records included in a batch is leading to an error suspending the certification, then the process is stopped for the whole batch.
There is no way to let the certification know to bypass those 2 records and to continue the process for all others.
Hence why, I would advise instead to try and dig as much as possible on why those 2 records are suspending the job.
If you already tried everything in that regard, maybe you could play with the enricher filter to not include those records in the enricher scope in the first place.
Or implement a new validation that would reject those records if you want to handle them manually.
In the meantime, if you don't want this suspension to block the integration queue, you can deactivate the option "suspend on error":
The problem with the 2 records is the use of Chinese characters in the alphabet. We were able to ask for the source system to be changed to the Latin alphabet this time, but we were hoping there was a different way to handle this situation if it happens again.
Danny ACKROYD
Our xDM instance includes a Google Maps API enricher for addresses. We have a couple of records that are written in Chinese characters. These records cause the API to return a 400, which suspends the job.
Is there some way to have the job otherwise succeed and just have those two records fail? Or is it intentional that the entire job fails if any record cannot be enriched?
Hello Danny,
If one of the records included in a batch is leading to an error suspending the certification, then the process is stopped for the whole batch.
There is no way to let the certification know to bypass those 2 records and to continue the process for all others.
Hence why, I would advise instead to try and dig as much as possible on why those 2 records are suspending the job.
If you already tried everything in that regard, maybe you could play with the enricher filter to not include those records in the enricher scope in the first place.
Or implement a new validation that would reject those records if you want to handle them manually.
In the meantime, if you don't want this suspension to block the integration queue, you can deactivate the option "suspend on error":
https://www.semarchy.com/doc/semarchy-xdm/xdm/latest/Manage/execution/execution-engine.html#:~:text=of%20this%20cluster.-,Suspend%20on%20Error,-%3A%20Defines%20the%20behavior
Hope that helps
- Oldest First
- Popular
- Newest First
Sorted by Oldest FirstAlexia SIMOND
Hello Danny,
If one of the records included in a batch is leading to an error suspending the certification, then the process is stopped for the whole batch.
There is no way to let the certification know to bypass those 2 records and to continue the process for all others.
Hence why, I would advise instead to try and dig as much as possible on why those 2 records are suspending the job.
If you already tried everything in that regard, maybe you could play with the enricher filter to not include those records in the enricher scope in the first place.
Or implement a new validation that would reject those records if you want to handle them manually.
In the meantime, if you don't want this suspension to block the integration queue, you can deactivate the option "suspend on error":
https://www.semarchy.com/doc/semarchy-xdm/xdm/latest/Manage/execution/execution-engine.html#:~:text=of%20this%20cluster.-,Suspend%20on%20Error,-%3A%20Defines%20the%20behavior
Hope that helps
Danny ACKROYD
Thank you for your response.
The problem with the 2 records is the use of Chinese characters in the alphabet. We were able to ask for the source system to be changed to the Latin alphabet this time, but we were hoping there was a different way to handle this situation if it happens again.
-
Import Data Into Entities via Azure Data Lake
-
Recover Deleted(soft Delete) Record and Configure in Application
-
Data Quality in batch mode and real-time integration
-
Integration with analytics tools
-
Query/Load/Delete data with the REST API
-
Does the Done Tab in Inbox have a limit?
-
How Can I Trigger Enricher or Sql Procedure when deleting?
-
Matching Rules But Only The Latest Record Creates a Golden Record
-
Unstructured and Semi Structured Data in Semarchy?
-
Read CSV files from AWS S3
See all 79 topics