Why does my Amazon Athena query fail with the error "HIVE_BAD_DATA: Error parsing field value for field X: For input string: "12312845691""?
"When I query data in Amazon Athena, I get an error similar to one of the following:"HIVE_BAD_DATA: Error parsing field value for field X: For input string: "12312845691""HIVE_BAD_DATA: Error parsing column '0': target scale must be larger than source scale""
"When I query data in Amazon Athena, I get an error similar to one of the following:"HIVE_BAD_DATA: Error parsing field value for field X: For input string: "12312845691""HIVE_BAD_DATA: Error parsing column '0': target scale must be larger than source scale"Short descriptionThere are several versions of the HIVE_BAD_DATA error. If the error message specifies a null or empty input string (for example, "For input string: """), see Why do I get the error "HIVE_BAD_DATA: Error parsing field value '' for field X: For input string: """ when I query CSV data in Amazon Athena?Errors that specify an input string with a value occur under one of the following conditions:The data type defined in the table definition doesn't match the actual source data.A single field contains different types of data (for example, an integer value for one record and a decimal value for another record).ResolutionIt's a best practice to use only one data type in a column. Otherwise, the query might fail. To resolve errors, be sure that each column contains values of the same data type, and that the values are in the allowed ranges.If you still get errors, change the column's data type to a compatible data type that has a higher range. If you can't solve the problem by changing the data type,then try the solutions in the following examples.Example 1Source format: JSONIssue: In the last record, the "id" key value is "0.54," which is the DECIMAL data type. However, for the other records, the "id" key value is set to INT.Source data:{ "id" : 50, "name":"John" }{ "id" : 51, "name":"Jane" }{ "id" : 53, "name":"Jill" }{ "id" : 0.54, "name":"Jill" }Data Definition Language (DDL) statement:CREATE EXTERNAL TABLE jsontest_error_hive_bad_data (    id INT,    name STRING)ROW FORMAT SERDE 'org.openx.data.jsonserde.JsonSerDe'WITH SERDEPROPERTIES ( 'ignore.malformed.json' = 'true')LOCATION 's3://awsexamplebucket/jsontest_error_hive_bad_data/';Data Manipulation Language (DML) statement:SELECT * FROM jsontest_error_hive_bad_dataError:Your query has the following error(s):HIVE_BAD_DATA: Error parsing field value '0.54' for field 0: For input string: "0.54"This query ran against the "default" database, unless qualified by the query. Please post the error message on our forum or contact customer support with Query Id: bd50793b-94fc-42a7-b131-b7c81da273b2.To resolve this issue, redefine the "id" column as STRING. The STRING data type can correctly represent all values in this dataset. Example:CREATE EXTERNAL TABLE jsontest_error_hive_bad_data_correct_id_data_type (    id STRING,    name STRING)ROW FORMAT SERDE 'org.openx.data.jsonserde.JsonSerDe'WITH SERDEPROPERTIES ( 'ignore.malformed.json' = 'true')LOCATION 's3://awsexamplebucket/jsontest_error_hive_bad_data/';DML statement:SELECT * FROM jsontest_error_hive_bad_data_correct_id_data_typeYou can also CAST to the desired data type. For example, you can cast a string as an integer. However, depending on the data types that you are casting from and to, this might return null or inaccurate results. Values that can't be cast are discarded. For example, casting the string value "0.54" to INT returns null results:SELECT TRY_CAST(id AS INTEGER) FROM jsontest_error_hive_bad_data_correct_id_data_typeExample output:Results     _col01    502    513    534The output shows that the value "0.54" was discarded. You can't cast that value directly from a string to an integer. To resolve this issue, use COALESCE to CAST the mixed type values in the same column as the output. Then, allow the aggregate function to run on the column. Example:SELECT COALESCE(TRY_CAST(id AS INTEGER), TRY_CAST(id AS DECIMAL(10,2))) FROM jsontest_error_hive_bad_data_correct_id_data_typeOutput:Results     _col01    50.002    51.003    53.004    0.54Run aggregate functions:SELECT SUM(COALESCE(TRY_CAST(id AS INTEGER), TRY_CAST(id AS DECIMAL(10,2)))) FROM jsontest_error_hive_bad_data_correct_id_data_typeOutput:_col01    154.54Example 2Source format: JSONIssue: The "id" column is defined as INT. Athena couldn't parse "49612833315" because the range for INT values in Presto is -2147483648 to 2147483647.Source data:{ "id" : 50, "name":"John" }{ "id" : 51, "name":"Jane" }{ "id" : 53, "name":"Jill" }{ "id" : 49612833315, "name":"Jill" }DDL statement:CREATE EXTERNAL TABLE jsontest_error_hive_bad_data_sample_2 (    id INT,    name STRING)ROW FORMAT SERDE 'org.openx.data.jsonserde.JsonSerDe'WITH SERDEPROPERTIES ( 'ignore.malformed.json' = 'true')LOCATION 's3://awsexamplebucket/jsontest_error_hive_bad_data_2/';DML statement:SELECT * FROM jsontest_error_hive_bad_data_sample_2Error:Your query has the following error(s):HIVE_BAD_DATA: Error parsing field value '49612833315' for field 0: For input string: "49612833315"This query ran against the "default" database, unless qualified by the query. Please post the error message on our forum or contact customer support with Query Id: 05b55fb3-481a-4012-8c0d-c27ef1ee746f.To resolve this issue, define the "id" column as BIGINT, which can read the value "49612833315." For more information, see Integer types.Modified DDL statement:CREATE EXTERNAL TABLE jsontest_error_hive_bad_data_sample_2_corrected (    id BIGINT,    name STRING)ROW FORMAT SERDE 'org.openx.data.jsonserde.JsonSerDe'WITH SERDEPROPERTIES ( 'ignore.malformed.json' = 'true')LOCATION 's3://awsexamplebucket/jsontest_error_hive_bad_data_2/';Example 3Source format: JSONIssue: The input data is DECIMAL and the column is defined as DECIMAL in the table definition. However, the scale is defined as 2, which doesn't match the "0.000054" value. For more information, see DECIMAL or NUMERIC type.Source data:{ "id" : 0.50, "name":"John" }{ "id" : 0.51, "name":"Jane" }{ "id" : 0.53, "name":"Jill" }{ "id" : 0.000054, "name":"Jill" }DDL statement:CREATE EXTERNAL TABLE jsontest_error_hive_bad_data_sample_3(    id DECIMAL(10,2),    name STRING)ROW FORMAT SERDE 'org.openx.data.jsonserde.JsonSerDe'WITH SERDEPROPERTIES ( 'ignore.malformed.json' = 'true')LOCATION 's3://awsexamplebucket/jsontest_error_hive_bad_data_3/';DML statement:SELECT * FROM jsontest_error_hive_bad_data_sample_3Error:Your query has the following error(s):HIVE_BAD_DATA: Error parsing column '0': target scale must be larger than source scaleThis query ran against the "default" database, unless qualified by the query. Please post the error message on our forum or contact customer support with Query Id: 1c3c7278-7012-48bb-8642-983852aff999.To resolve this issue, redefine the column with a scale that captures all input values. For example, instead of (10,2), use (10,7).CREATE EXTERNAL TABLE jsontest_error_hive_bad_data_sample_3_corrected(    id DECIMAL(10,7),    name STRING)ROW FORMAT SERDE 'org.openx.data.jsonserde.JsonSerDe'WITH SERDEPROPERTIES ( 'ignore.malformed.json' = 'true')LOCATION 's3://awsexamplebucket/jsontest_error_hive_bad_data_3/';Follow"