Overview
This node allows users to run SQL queries against an AWS Athena database. It is useful for retrieving data from large datasets stored in Amazon S3 via Athena's serverless interactive query service. Typical use cases include data analysis, reporting, and integrating Athena query results into automated workflows.
For example, a user can specify a database and a SQL query to fetch sales data for the last month, then use the output in subsequent nodes for visualization or further processing.
Properties
| Name | Meaning |
|---|---|
| Database Name | The name of the Athena database where the query will be executed. |
| Query | The SQL query string to execute on the specified Athena database. Supports SQL editor. |
Output
The node outputs an array of JSON objects representing the rows returned by the Athena query. Each object’s keys correspond to the column names from the query result, and values are the respective cell values as strings.
If the query returns no rows, the output will be an empty array.
The node does not output binary data.
Dependencies
- Requires valid AWS credentials with access to Athena and the configured S3 bucket for query results.
- The credentials must include an access key ID, secret access key, and optionally a session token.
- The node uses the AWS SDK internally to communicate with Athena.
- The S3 output location for Athena query results must be configured in the credentials.
Troubleshooting
- Invalid Credentials Error: If the AWS access key or secret key is missing or incorrect, the node throws an error indicating invalid credentials. Ensure the API authentication token or keys are correctly set up.
- Query Execution Failure: If Athena fails to start or complete the query (e.g., syntax errors, permissions issues), the node reports the failure reason. Check the query syntax and AWS permissions.
- Long Running Queries: The node polls Athena until the query finishes. For very long queries, this may cause delays. Consider optimizing the query or using smaller datasets.
- S3 Output Location Issues: If the configured S3 bucket for query results is inaccessible or misconfigured, the query execution will fail. Verify the bucket exists and the credentials have write access.