Query Athena
Open a discovered Athena table, choose a query-result location, and run a filter-built statement or Athena SQL.
Choose a workgroup
Open query settings in the Athena tab. Dynomate lists workgroups for the active profile, account, and Region. It prefers the first enabled SQL workgroup with a result target. Spark workgroups are not available in this workflow.
Choose one result-output mode:
- Workgroup default: Use the workgroup S3 output or Athena managed query results.
- Custom S3 output: Enter an
s3://bucket/prefix/location.
Dynomate does not create or guess an output location. An enforced workgroup configuration can override a custom S3 setting.
Build or write a query
Filter mode
Select columns, add filter groups, choose AND or
OR, and set one sort column. Dynomate generates a
SELECT statement for the open table.
SQL mode
Enter Athena SQL. The editor suggests columns from discovered metadata. Dynomate sends the statement to Athena through the selected workgroup.
You can keep generated SQL when you move from Filter mode to SQL mode.
Conversion back to Filter mode supports one simple SELECT
for the current table. Joins, CTEs, unions, aggregates, grouping,
expression projections, limits, offsets, and multiple statements remain in SQL mode.
Control returned rows and cost
Max rows accepts values from 100 to 500,000. Dynomate
stops collecting results at that value. It also adds an outer
LIMIT when it can safely wrap one SELECT statement.
Max rows is not an Athena scan-cost limit.
Athena can scan source files before it applies a row limit. Partition pruning, query structure, file layout, compression, and workgroup limits determine scanned bytes and cost. Review scanned bytes after each run.
Run a query
- Confirm the profile, Region, catalog, database, and table.
- Confirm the workgroup and result-output mode.
- Select Run.
- Wait for a succeeded, failed, cancelled, or timed-out state.
Dynomate polls Athena once per second for the first 10 seconds, then once every two seconds. It stops waiting after 10 minutes and requests cancellation.
Cancel a query
Select Cancel to call StopQueryExecution.
Dynomate waits up to 30 seconds for a terminal Athena state. Closing a
running Athena tab also sends a best-effort cancellation request.
Cancellation is not immediate. Athena can remain queued or running after Dynomate sends the request. Check Athena when cost or side effects matter. A cancelled or failed run does not create a partial result in Dynomate.
Required permissions
Dynomate calls these AWS actions to run and cancel Athena queries:
sts:GetCallerIdentityathena:StartQueryExecutionathena:GetQueryExecutionathena:GetQueryResultsathena:StopQueryExecution
Athena can require access to the source catalog and data. The selected result location can require S3 and KMS access. Workgroup and Lake Formation policies still apply. Dynomate does not request broader service actions unless the selected query or workgroup requires them.
Open Logs to review Athena calls and failures.