1 Kommentar
If you are confident that your input files have the correct DDB JSON import format and you have correctly configured the import job format and file compression settings, this problem can arise from invalid JSON items.
Try downloading the S3 object that is failing to import and using jq to parse it to detect invalid JSON.
This bash snippet will process each line in the file, printing any parsing errors jq encounters as debug messages:
# INFO: Tested working with jq-1.8.1 on Amazon Linux 2
cat your_s3_object_file.jsonl | jq -R 'try fromjson catch debug | empty''
Input used to test this method (note, 2nd line is valid, first and 3rd are not):
"\m"
"\n"
"\o"
Output observed (note, final error arises from endline-terminated file containing a single empty string input)
["DEBUG:","Invalid escape at line 1, column 4 (while parsing '\"\\m\"')"]
["DEBUG:","Invalid escape at line 1, column 4 (while parsing '\"\\o\"')"]
["DEBUG:","Expected JSON value (while parsing '')"]
beantwortet vor 3 Monaten
Relevanter Inhalt
- AWS OFFICIALAktualisiert vor 3 Jahren
- AWS OFFICIALAktualisiert vor 10 Monaten
