Skip to content
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

AWS Glue: BIGQUERY connection type support #5247

Closed
ksauzz opened this issue Apr 30, 2024 · 6 comments
Closed

AWS Glue: BIGQUERY connection type support #5247

ksauzz opened this issue Apr 30, 2024 · 6 comments
Assignees
Labels
bug This issue is a bug.

Comments

@ksauzz
Copy link

ksauzz commented Apr 30, 2024

Describe the bug

aws-sdk-go doesn't accept BIGQUERY as connection type because API specification file seems too old.

According to the blog post, AWS Glue has suppported BIGQUERY since Oct 2023, but the API version is 2017-03-31.

Expected Behavior

aws-sdk-go accepts BIGQUERY as connection type.

Current Behavior

Error: expected connection_type to be one of ["JDBC" "SFTP" "MONGODB" "KAFKA" "NETWORK" "MARKETPLACE" "CUSTOM"], got BIGQUERY

Reproduction Steps

See API Model.
https://github.com/aws/aws-sdk-go/blob/main/models/apis/glue/2017-03-31/api-2.json#L4942-L4953

Possible Solution

Update models/apis/glue/2017-03-31 to the latest one, and run make generate

Additional Information/Context

I couldn't find any newer glue API model in any SDK repositories.

SDK version used

1.51.31

Environment details (Version of Go (go version)? OS name and version, etc.)

all environment.

@ksauzz
Copy link
Author

ksauzz commented May 1, 2024

Our team decided to use spark-bigquery-connector in AWS Glue instead, so this issue is no longer necessary for us. Feel free to close this if no one has interest.

@RanVaknin
Copy link
Contributor

Hi @ksauzz ,

The SDK is code generated from the API model of each service. In this case, the source of truth for the enum type the SDK uses is the internal API model for glue which does not specify BIGQUERY as a valid enum value for connectionType.

According to the blog post, AWS Glue has suppported BIGQUERY since Oct 2023, but the API version is 2017-03-31.

The API version date you see here is when this major version was released, and is not related to when it was last updated. Since AFAIK Glue only has one major version supported, 2017-03-31 is when this major version was released.

From reading the blogpost I can see that this is indeed supported, but from an API operation perspective I don't see that BIGQUERY is mentioned anywhere under ConnectionType, not in the blogpost or any other service docs. To be clear, you might be 100% correct and the Glue service team simply did not update their API model to include this newly released type and we might need to engage with them to fix it.

I will reach out to confirm with the Glue team if this needs to be added and if so I'll have them update their model to include it.

Thanks,
Ran~

@RanVaknin RanVaknin self-assigned this May 2, 2024
@RanVaknin RanVaknin removed the needs-triage This issue or PR still needs to be triaged. label May 2, 2024
@ksauzz
Copy link
Author

ksauzz commented May 7, 2024

Thank you for the explanation in detail.

@RanVaknin
Copy link
Contributor

Hi there,

I was not able to get a confirmation from the Glue team on whether this is the intended value for this enum or whether this value has service side support to begin with.

If anyone is running into this issue in the future, please open a separate issue on our v2 SDK repository issue queue.

Thanks,
Ran~

@RanVaknin RanVaknin closed this as not planned Won't fix, can't repro, duplicate, stale May 23, 2024
Copy link

Comments on closed issues are hard for our team to see.
If you need more assistance, please either tag a team member or open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.

@ksauzz
Copy link
Author

ksauzz commented May 24, 2024

I think some users want to manage BIGQUERY connection type through terraform involving aws-sdk-go v1, as well as v2 someday. So even without updating API model, just removing client-side validation for the enum would help them.

Thanks.

hashicorp/terraform-provider-aws#34575

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug This issue is a bug.
Projects
None yet
Development

No branches or pull requests

2 participants