Documentation

Query Amazon Athena

To query Amazon Athena with Flux:

  1. Import the sql package.

  2. Use sql.from() and provide the following parameters:

    • driverName: awsathena
    • dataSourceName: See data source name
    • query: SQL query to execute
import "sql"

sql.from(
    driverName: "awsathena",
    dataSourceName:
        "s3://myorgqueryresults/?accessID=12ab34cd56ef&region=region-name&secretAccessKey=y0urSup3rs3crEtT0k3n",
    query: "GO SELECT * FROM Example.Table",
)

Amazon Athena data source name

The awsathena driver uses the following data source name (DSN) syntaxes (also known as a connection string):

s3://myorgqueryresults/?accessID=AKIAJLO3F...&region=us-west-1&secretAccessKey=NnQ7MUMp9PYZsmD47c%2BSsXGOFsd%2F...
s3://myorgqueryresults/?accessID=AKIAJLO3F...&db=dbname&missingAsDefault=false&missingAsEmptyString=false&region=us-west-1&secretAccessKey=NnQ7MUMp9PYZsmD47c%2BSsXGOFsd%2F...&WGRemoteCreation=false

Use the following query parameters in your Athena S3 DSN:

* Required
  • * region - AWS region
  • * accessID - AWS IAM access ID
  • * secretAccessKey - AWS IAM secret key
  • db - database name
  • WGRemoteCreation - controls workgroup and tag creation
  • missingAsDefault - replace missing data with default values
  • missingAsEmptyString - replace missing data with empty strings

Athena to Flux data type conversion

sql.from() converts Athena data types to Flux data types.

Athena data typeFlux data type
tinyint, smallint, int, integer, bigintint
float, double, realfloat
timestamp with time zonetime
booleanbool

All other Athena data types (including timestamp, date and time) are converted to strings.


Was this page helpful?

Thank you for your feedback!


The future of Flux

Flux is going into maintenance mode. You can continue using it as you currently are without any changes to your code.

Flux is going into maintenance mode and will not be supported in InfluxDB 3.0. This was a decision based on the broad demand for SQL and the continued growth and adoption of InfluxQL. We are continuing to support Flux for users in 1.x and 2.x so you can continue using it with no changes to your code. If you are interested in transitioning to InfluxDB 3.0 and want to future-proof your code, we suggest using InfluxQL.

For information about the future of Flux, see the following: