LogoLogo
OverviewQuickstartsHow To GuidesReferenceArticlesSupport
Support
Support
  • Support
  • FAQs
    • Get Started with Upsolver
    • Basic Elements of Upsolver
    • Iceberg Cloud Storage Breakdown
    • Infrastructure
    • Cost Estimator
  • TROUBLESHOOTING
    • AWS Configuration
      • CloudFormation Stack Failed to Deploy
      • Private API Doesn't Start or Can't Connect
        • Elastic IPs Limit Reached
        • EC2 Spot Instance Not Running
        • DNS Cache
        • Security Group Not Open
    • Cluster
      • Compute Cluster Doesn't Start
      • Can't Connect to Apache Kafka Cluster
    • Jobs
      • Problem Ingesting Amazon S3 Data
      • Data Doesn't Appear in Athena Table
      • Exception When Querying Athena Table
  • ERROR MESSAGES
    • Error Messages
      • Cluster
        • UP10020 COMPUTE_CLUSTER is Missing
      • Jobs
        • UP10010 Missing ON Condition
        • UP10030 Entity Already Exists
        • UP10040 Entity Not Found
        • UP10050 Materialized View Illegal Column Expression
        • UP10060 Statement Parsing
        • UP10100 Cannot Select Records in an UNNEST Statement
        • UP20010 Source Data Not Found
        • UP20040 Could Not DROP Entity Used by a Job or Materialized View
      • Replication
        • UP20050 Reached PostgreSQL Replication Slots Limit
        • UP20051 PostgreSQL Replication is Disabled
      • Security
        • UP20020 No Access to Database
        • UP20030 No Permissions to assumeRole
        • UP20060 Unable to Connect
        • UP20061 Unable to Connect to a Private Network
Powered by GitBook
On this page
  1. TROUBLESHOOTING
  2. Jobs

Exception When Querying Athena Table

Last updated 11 months ago

The most common reason why querying an Athena table fails is that the user performing the query doesn't have access to the files in Amazon S3.

Make sure you have read access to the target location that Upsolver is writing to.

If the issue is still not resolved, please raise a ticket via the .

Upsolver Support Portal