Closed ifeanyeg closed 10 years ago
This issue occurred only in the server. To solve this issue a decision has been taken to divide the original batch ingesting process into 2 parts.
First part will be executed on an environment which doesn't have the above mentioned problem. Second part will be executed on the server.
Hi Lloyd,
There are some characters in some of the records that makes the batch ingester to fail when ingesting records ( e.g. —). The error message is show below: UnicodeDecodeError: 'ascii' codec can't decode byte 0xe2 in position 17: ordinal not in range(128)
Is there a way to skip such records or make the batch ingester to decode such character?
Regards, Ifeanyi