Athena v3 error message not as descriptive as v2

Question

When running queries on Athena v3 I get vague error messages.  When the same query is run on v2, error are specific including the correct line number and what the error is.  Is there a setting to enable the v3 messages to be as descriptive as v2?

For example this is returned when creating a table in v2:  Error parsing field value '' for field 2: For input string: ""
vs v3: Cannot convert value of type String to a LONG value

It's clear the 2nd column of data is the one w/ the error vs ambiguous error on which column for v3

Answer

Hello There,

Thank you for your query.

I understand that you have observed different error messages in v2 and v3 for a Create table statement error in Athena, where the message in v2 is more descriptive and informative than v3. You would like to understand if there is any setting that needs to be enabled to get more descriptive message on v3.

As per my understanding there is no setting that needs to be enabled. However we need to understand if the error message is different for this scenario only or if its same for different types of query as well and see if any changes might be required on Athena query engine. In order to do so, I would request you to log a support case with Athena team, where we can look further into the query details and analyse the issue and action accordingly.

Please feel free to reach out if you would like any clarity on the above approach.

Hope you have a great day ahead.

Athena v3 error message not as descriptive as v2

Relevanter Inhalt