Documentation

The amount of data scanned during the query execution and the amount of time that it took to execute, and the type of statement that was run.

See: newQueryExecutionStatistics smart constructor.

Create a value of QueryExecutionStatistics with all optional fields omitted.

Use generic-lens or optics to modify other optional fields.

The following record fields are available, with the corresponding lenses provided for backwards compatibility:

$sel:totalExecutionTimeInMillis:QueryExecutionStatistics', queryExecutionStatistics_totalExecutionTimeInMillis - The number of milliseconds that Athena took to run the query.

$sel:engineExecutionTimeInMillis:QueryExecutionStatistics', queryExecutionStatistics_engineExecutionTimeInMillis - The number of milliseconds that the query took to execute.

$sel:queryPlanningTimeInMillis:QueryExecutionStatistics', queryExecutionStatistics_queryPlanningTimeInMillis - The number of milliseconds that Athena took to plan the query processing flow. This includes the time spent retrieving table partitions from the data source. Note that because the query engine performs the query planning, query planning time is a subset of engine processing time.

$sel:dataScannedInBytes:QueryExecutionStatistics', queryExecutionStatistics_dataScannedInBytes - The number of bytes in the data that was queried.

$sel:queryQueueTimeInMillis:QueryExecutionStatistics', queryExecutionStatistics_queryQueueTimeInMillis - The number of milliseconds that the query was in your query queue waiting for resources. Note that if transient errors occur, Athena might automatically add the query back to the queue.

$sel:dataManifestLocation:QueryExecutionStatistics', queryExecutionStatistics_dataManifestLocation - The location and file name of a data manifest file. The manifest file is saved to the Athena query results location in Amazon S3. The manifest file tracks files that the query wrote to Amazon S3. If the query fails, the manifest file also tracks files that the query intended to write. The manifest is useful for identifying orphaned files resulting from a failed query. For more information, see Working with Query Results, Output Files, and Query History in the Amazon Athena User Guide.

$sel:serviceProcessingTimeInMillis:QueryExecutionStatistics', queryExecutionStatistics_serviceProcessingTimeInMillis - The number of milliseconds that Athena took to finalize and publish the query results after the query engine finished running the query.

The number of milliseconds that Athena took to run the query.

The number of milliseconds that the query took to execute.

The number of milliseconds that Athena took to plan the query processing flow. This includes the time spent retrieving table partitions from the data source. Note that because the query engine performs the query planning, query planning time is a subset of engine processing time.

The number of bytes in the data that was queried.

The number of milliseconds that the query was in your query queue waiting for resources. Note that if transient errors occur, Athena might automatically add the query back to the queue.

The location and file name of a data manifest file. The manifest file is saved to the Athena query results location in Amazon S3. The manifest file tracks files that the query wrote to Amazon S3. If the query fails, the manifest file also tracks files that the query intended to write. The manifest is useful for identifying orphaned files resulting from a failed query. For more information, see Working with Query Results, Output Files, and Query History in the Amazon Athena User Guide.

The number of milliseconds that Athena took to finalize and publish the query results after the query engine finished running the query.