This repository has been archived by the owner on Dec 22, 2020. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 224
String not valid UTF-8 (BSON::InvalidStringEncoding) #92
Comments
any update on this one? |
I had the same issue. I just monkey patched it to remove the invalid k,v from the obj. I replaced the The ETL errors from my data were caused by binary values and larger than expected BSON documents.
|
+1 - anyone know what would cause this? I checked the timestamp that it appears to be failing on and I don't see any issues |
looks like there was a PR open to resolve this here: #83 which broke tests. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I have the following exception when importing a collection, the data should be valid since it is already present in the database.
Any ideas?
Please note this is failing even with the --unsafe flag.
The text was updated successfully, but these errors were encountered: