I had the error: cannot be resolved or requester is not authorized to access requested resources This query ran against the "default" database, unless qualified by the query.

0

I use athena to do direct query in quicksight, I have a table in dynamodb called history and in that table I have a column called "management", it was added recently but my athena does not reflect it And when I try to select Manage from history I get the error: COLUMN_NOT_FOUND: line 1:8: Column 'manage' cannot be resolved or requester is not authorized to access requested resources 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: 0639ed2a-4692-49af-968e-2fa61a1fec82

Joann
asked 2 months ago616 views
3 Answers
1

I think you need to refresh the schema in Athena. You can do this by running this command to update the table metadata:

MSCK REPAIR TABLE history;

After running the MSCK REPAIR TABLE command, you can verify that the "management" column is now included in the schema by running:

DESCRIBE history;

NOTE: If you're still facing issues after trying these steps, make sure that your IAM permissions are correctly set up to allow Athena to access your DynamoDB table.

Resources:

profile picture
EXPERT
answered 2 months ago
  • I had this error: Unsupported DDL for Lambda catalogs: 'MSCK REPAIR TABLE history'

0

Hello,

From the error seems like Athena does not have information like serde about table. Generally Athena support to query s3 datasources directly using AWS Glue Data Catalog. If you have sources other than s3 then you can consider to use Athena Federated query.

https://docs.aws.amazon.com/athena/latest/ug/connect-to-a-data-source.html

In your case, i suspect table created on dynamodb source using crawler and you can check table classification it shows dynamodb. If you use crawler to create the table in Glue catalog for sources other than s3 like dynamodb in your case then Athena will not be able to query the table directly and generally failed with the error you mentioned.

Hence i would suggest to verify the table properties like classification to know if table is created using crawler or not. If this is the case then Athena query does not work directly and you can use Athena Federated query feature to query external sources like dynamodb.

AWS
answered 2 months ago
  • I used : AthenaDynamoDBConnector with Athena Federated query

0

Hello Joann,

Regarding this error Unsupported DDL for Lambda catalogs: 'MSCK REPAIR TABLE history' you faced is means that you are using Athena Federated query method which uses lambda to get the data from exteral sources.

Hence in case of federated query you cant run MSCK REPAIR TABLE tablename. MSCK REPAIR TABLE command is used to load the hive style partitions in Glue data catalog table for s3 sources only. It will not work for external sources.

AWS
answered 2 months ago
  • Is there any other solution for this error:cannot be resolved or requester is not authorized to access requested resources This query ran against the "default" database, unless qualified by the query. ?

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions

Relevant content