-
Notifications
You must be signed in to change notification settings - Fork 721
feat: always use a default workgroup config, instead of retrieving a workgroup config from the AWS API #3237
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
feat: always use a default workgroup config, instead of retrieving a workgroup config from the AWS API #3237
Conversation
…oup config from AWS API
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
|
Looks like a few test cases failed with the error: From my analysis, the issue is in how we override s3_output: Since we are not fetching wg_config anymore, we do not know if the workgroup config is enforced until we submit the query. We are however overriding s3_output, that might confict with enforced workgroup config. I think we might want to deprecate |
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
|
@kukushking agreed - if the user passed an S3 output, it should be included in start query execution, otherwise nothing should be passed for S3 output (so the workgroup definitions will take place). I'll make the code change |
…_output if passed by user. For queries that require a location, keep previous impl of s3_output either by user or by workgroup setting
| execution_params: list[str] | None, | ||
| ) -> _QueryMetadata: | ||
| wg_config: _WorkGroupConfig = _get_workgroup_config(session=boto3_session, workgroup=workgroup) | ||
| wg_config: _WorkGroupConfig = _get_workgroup_config(workgroup=workgroup, session=boto3_session) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Unload requires a TO location, so keeping the previous implementation here, but added an exception in case we don't have S3 output from either user or workgroup
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
Feature or Bugfix
Detail
Remove redundant call to AWS API in order to get the workgroup config, as it will take place anyways if not overridden by the client
Relates
Issue #3233
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.