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

Create an Official Beam I/O Connector for Cloud SQL #1062

Open
FearTheMonstar opened this issue Apr 12, 2024 · 2 comments
Open

Create an Official Beam I/O Connector for Cloud SQL #1062

FearTheMonstar opened this issue Apr 12, 2024 · 2 comments
Assignees
Labels
priority: p2 Moderately-important priority. Fix may not be included in next release. type: feature request ‘Nice-to-have’ improvement, new feature or different behavior or design.

Comments

@FearTheMonstar
Copy link

Feature Description

The current Cloud SQL Python connector is great. But in it's current form, when used via Apache Beam/Google Cloud Dataflow, it is not recognized as an official Apache Beam framework construct. This can lead to unbalanced workers in Dataflow when dealing with any kind of volume in a pipeline.

I suggest creating an official Beam I/O Connector so that Cloud SQL can have optimized usage with Beam/Dataflow.

Sample code

No response

Alternatives Considered

There is current non-native Cloud SQL support, but it requires a custom container. This can cause slowdowns and longer approval processes at regulated customers. An official native I/O connector would be ideal.

Additional Details

No response

@FearTheMonstar FearTheMonstar added the type: feature request ‘Nice-to-have’ improvement, new feature or different behavior or design. label Apr 12, 2024
@jackwotherspoon jackwotherspoon added the priority: p1 Important issue which blocks shipping the next release. Will be fixed prior to next release. label Apr 12, 2024
@jackwotherspoon jackwotherspoon changed the title Modify/Create a New Connector as an Official Beam I/O Connector Create an Official Beam I/O Connector for Cloud SQL Apr 12, 2024
@jackwotherspoon
Copy link
Collaborator

Thanks for raising the issue! We will chat with stakeholders and monitor any upvotes here to help prioritize this potential work.

Related to #1057

@danvau7
Copy link

danvau7 commented Apr 12, 2024

Would like to add 1 upvote to this item :)

@jackwotherspoon jackwotherspoon added priority: p2 Moderately-important priority. Fix may not be included in next release. and removed priority: p1 Important issue which blocks shipping the next release. Will be fixed prior to next release. labels May 31, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority: p2 Moderately-important priority. Fix may not be included in next release. type: feature request ‘Nice-to-have’ improvement, new feature or different behavior or design.
Projects
None yet
Development

No branches or pull requests

3 participants