I have an int stored in my s3 file and the table has int as a type. However, randomly athena seems to be adding a .0 to the end of the int for some files and not others and returning the following error:
'HIVE_BAD_DATA: Error reading field value: For input string: "638.0"
This query ran against the ‘***********' database, unless qualified by the query. Please post the error message on our forum or contact customer support with Query ID: 86d934ea-4c17-4f41-af4b-a87f50bba7be'
However, I checked the file in question and the value is definitely:
"stay_duration_in_days": 638
I noticed also other values such as id which is also randomly for some files getting .0 added to it even though its stored in the file as: id": 5496946851911,
Has anyone seen this behaviour before?
