- Newest
- Most votes
- Most comments
Hello.
It is difficult to judge from the error message alone, but it may occur if there is a problem with the syntax of the query actually used or a problem with the performance of Athena.
The blog below reports that a similar error occurs when there is a mistake in the S3 URL listed in the query.
Errors can occur due to mistakes like this, so I think it's a good idea to first check that there are no problems with the syntax in the query.
https://icesquare.com/wordpress/amazon-athenaerrorcode-internal_error_query_engine-amazon-athena-experienced-an-internal-error-while-executing-this-query-please-contact-aws-support-for-further-assistance-you-will-not-be-charg/
Thanks for the help I think this is an issue with the size of the query as it is generated from a template and the biggest difference is the size.
Also the problem only happens with the last join, I was hoping someone could look at the query execution based on the id and let me know what the 'Internal Error' actually was
Relevant content
- Accepted Answerasked a year ago
- asked 2 years ago
- AWS OFFICIALUpdated a month ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 2 months ago
- AWS OFFICIALUpdated 9 months ago
Thank you for your reply. With re:Post, you cannot check the content of the query from the query ID, so you will need to open a case with AWS Support under "Technical". Please note that technical support is paid support. https://docs.aws.amazon.com/awssupport/latest/user/case-management.html