- Newest
- Most votes
- Most comments
The INTERNAL_ERROR_QUERY_ENGINE error you're experiencing is an internal Athena error that occurs on the query engine side. This type of error is not typically caused by user input but rather by an issue within Athena's system itself.
Here are a few steps you can try to resolve this issue:
-
Retry the query: Sometimes, these internal errors are transient and can be resolved by simply running the query again.
-
Check your data: Ensure that the table 'covid_enigma_jhu_bucket' exists in your specified schema and has the expected structure.
-
Verify the S3 location: Make sure the S3 location for storing query results is correctly configured and accessible. Include a trailing slash (/) at the end of the S3 path.
-
Check permissions: Ensure that your IAM user or role has the necessary permissions to access both the source data and the query results location.
-
Simplify the query: If possible, try running a simpler query (e.g., SELECT a few specific columns instead of *) to see if the error persists.
-
Check Athena service status: Verify if there are any ongoing issues with the Athena service in your region.
If the problem persists after trying these steps, you may need to contact AWS support for further assistance, as the error message suggests. They have access to more detailed logs and can investigate the root cause of the internal error.
Remember, you won't be charged for queries that result in this error, so don't hesitate to retry or experiment with query modifications to resolve the issue.
Sources
ATHENA INTERNAL_ERROR_QUERY_ENGINE | AWS re:Post
S3 LOCATION INvalid | AWS re:Post
Relevant content
asked 3 years ago
