schema name was not found when running a query lambda function into Athena. However, when running in Athena it works
0
schema name was not found when running a query lambda function into Athena. However, when running the same exact query in Athena it works (see attachment)
1 réponse
- Le plus récent
- Le plus de votes
- La plupart des commentaires
0
Is your boto3.client for the right region and account? Regio nwill be picked up from your environment or you can specify it to boto3.client('athena', region_name).
Contenus pertinents
- demandé il y a un an
- demandé il y a un an
- demandé il y a 6 mois
AWS OFFICIELA mis à jour il y a un an- AWS OFFICIELA mis à jour il y a 3 ans
- AWS OFFICIELA mis à jour il y a 3 ans
ya its the right region and account, tried stating the region name, still returning the same error :/
Out of curiosity I tried pretty much exactly what you're doing and it worked fine until I deliberately put a wrong schema name in the query, then I got your error. I'm stumped, I can't think of anything else that could be wrong.