fix: Support Athena workgroups with managed query results (#3174)#3275
Open
fix: Support Athena workgroups with managed query results (#3174)#3275
Conversation
Contributor
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
Contributor
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
Contributor
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Feature or Bugfix
Detail
ManagedQueryResultsConfigurationand conditionally omittingResultConfigurationfromStartQueryExecutionAPI callsGetQueryResultsAPI-based result reader (_fetch_api_result) to read results from Athena-owned storage when no S3OutputLocationis available, with support for both full and chunked reads_get_s3_output()call (and its bucket-creation side effect) in the regular query path when managed results is enabledresult_reuse_configurationis not used with managed results workgroups, as AWS does not support this combinationget_query_results()and cached-result paths through the API result reader whenoutput_locationisNones3_outputdocstrings onstart_query_executionandread_sql_queryto document managed results behaviourRelates
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.