An Amazon Athena source reads tables from Athena into the Lake. Its form has three steps, General, Connection and Review: sign in with an IAM user key, choose the region and the output location, and check the datetime settings before you save.
Once the source is saved, import its tables.
The AWS credentials card takes the IAM user key the source signs in with:
AKIA….The card notes: "An IAM user key with Athena, Glue Data Catalog and S3 access to the data and the output location."
After you save, the form never shows the secret again: the field keeps a stored value with Replace beside it. If your administrator turned on re-entering connector secrets and you change AWS Access Key ID, the form asks for the secret access key again. Stored secrets and the test card behave as on the other connector forms; Connect a SQL database describes both.
The Query results card sets where the queries run:
Search region code or city…) and pick an option such as us-east-1 · US East (N. Virginia). Before you pick, the field reads Select the AWS region; a search with no match reads No matching region.s3:/ / my-bucket/ athena-results/. The field notes: "Athena writes query results here. A trailing / is added if missing."If a saved source uses a region that is not in the picker's list, the form keeps it as the selected option, so an edit never drops it.
The form names each required field you leave empty:
An output location that is not an S3 location is refused with Use an S3 location such as s3://my-bucket/athena-results/. The address must start with s3:/, name a bucket and contain no spaces.
The Review step shows the summary of the new source: Name, Access key ID, Region and Output location. A field you left empty reads as -; the secret access key is never shown.
The Source timezone: row starts collapsed. A new Athena source starts with the timezone set to UTC and keeps datetime values as written, so the row reads UTC (Athena always runs in UTC). Click Change to open the Source datetime settings and pick another timezone or change how datetime values are read. Timezones and datetime values explains both settings and the rules that always apply.
The submit button reads Add for a new source, Save in edit mode and Duplicate for a copy.
When a load runs, DataMind runs a query in Athena and loads the rows the query returns. The query reads the columns you synced for the table.
If the table has a WHERE clause for sync, the clause is applied inside that query, so Athena filters the rows on the table's raw column values before they are read out. Set the clause on the table's Conditions step; Configure a table describes it.
A load can stop with one of these messages:
INFORMATION_SCHEMA, and either one is refused. Rework the query without them.See Run, stop and troubleshoot loads for the Sync Log and for Sync Schema, and Lake troubleshooting for the messages you may see while you connect.
An IAM user key with Athena, Glue Data Catalog and S3 access to the data and the output location. Enter its AWS Access Key ID and AWS Secret Access Key on the Connection step.
Athena writes query results there. Enter an S3 location such as s3:/; a trailing / is added if it is missing.
The field accepts an S3 location only: it must start with s3:/, name a bucket and contain no spaces. Anything else shows Use an S3 location such as s3://my-bucket/athena-results/.
Yes. When a saved region is not among the listed AWS regions, the form keeps it as the selected option, so an edit never drops it.
Athena runs its queries in UTC and a new source keeps datetime values as written, so the Source timezone: row shows that. Click Change to pick another timezone or change how values are read; see Timezones and datetime values.
A query in Athena: DataMind runs it, reads the columns you synced, and loads the rows the query returns.
Inside the query itself, on the table's raw column values, so Athena filters the rows before they are read out. Set the clause on the table's Conditions step (Configure a table).
The query the load would run ends with a semicolon or contains INFORMATION_SCHEMA, and either one is refused. Rework the query without them and run the load again.
The load cannot find the table it was set up for; the message continues with the table's database, schema and table name. Check that the table still exists in the source, run Sync Schema on the datasource, and run the load again.
The form opens on the Connection step, Name and Code are locked, and the submit button reads Save. Duplicate starts a copy with Name and Code empty.