- Newest
- Most votes
- Most comments
The ingestion error you're encountering with Bedrock metadata likely stems from invalid attribute keys or values in your metadata files.
Ensure that your metadata attributes adhere to the following guidelines: keys and values should not exceed the character limits, values must be of acceptable data types (strings, numbers, Booleans, or String Lists), and metadata should be properly formatted.
Double-check that the attributes conform to Bedrock's specifications and retry the ingestion process after making any necessary corrections.
Ensure that all attribute keys and values in your metadata files do not exceed the character limits set by the service. Typically, keys and values should be within a certain character length, usually around 255 characters. Review your metadata files for any unusually long attribute names or values. Confirm that all attribute values are of acceptable data types: strings, numbers, Booleans, or String Lists.
Write a Validation Script:
Create a script (in Python, Node.js, or your preferred language) to read each metadata file. Validate each attribute against the required schema (character length, data type, etc.). Log or flag any files that fail validation.
Correct Invalid Files:
Optionally, the script could also correct some common issues automatically, such as truncating long strings or converting data types where possible. For more complex corrections, the script can generate a report so you can manually review and fix only the problematic files.
Retry the Ingestion:
After running the script and correcting the files, retry the ingestion process.
Relevant content
- asked 2 years ago
- Accepted Answerasked a month ago
- AWS OFFICIALUpdated 3 months ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 3 years ago
Thanks for sharing. I have no string longer than 97 characters (the urls) and everything is strings.