1 Answer
- Newest
- Most votes
- Most comments
0
I had the same error. Turns out the problem had to do with an incorrect column data type. In my case, I specified INT against a column containing values greater than INT's max size of 2^31-1. Changing the column's data type to BIGINT or STRING fixed it for me.
answered 8 days ago
Relevant content
- asked 9 months ago
- asked a year ago
- AWS OFFICIALUpdated 3 months ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 3 months ago