Re: [DISCUSS] Externalized Google Cloud Connectors

2024-04-08 Thread Ahmed Hamdy
Hi Claire, I am in favor of Martijn and Leonard's points, it is better to follow aws connectors and keep it under ASF. Do you have other suggestions for connectors than pub/sub at the moment? Best Regards Ahmed Hamdy On Thu, 4 Apr 2024 at 08:38, Martijn Visser wrote: > Hi Lorenzo, > > Bahir is

Re: [DISCUSS] Externalized Google Cloud Connectors

2024-04-04 Thread Martijn Visser
Hi Lorenzo, Bahir is retired, see the homepage. It plays no role (anymore). > This, unfortunately, is the tradeoff for developing the connectors outside of Apache in exchange for development velocity. I understand that. It can be considered to develop the connectors outside of the Flink project

Re: [DISCUSS] Externalized Google Cloud Connectors

2024-04-03 Thread lorenzo . affetti
@Leonard @Martijn Following up on @Claire question, what is the role of Bahir (https://bahir.apache.org/) in this scenario? I am also trying to understand how connectors fir in the Flink project scenario :) Thank you, Lorenzo On Apr 2, 2024 at 06:13 +0200, Leonard Xu , wrote: > Hey, Claire > >

Re: [DISCUSS] Externalized Google Cloud Connectors

2024-04-01 Thread Leonard Xu
Hey, Claire Thanks starting this discussion, all flink external connector repos are sub-projects of Apache Flink, including https://github.com/apache/flink-connector-aws. Creating a flink external connector repo named flink-connectors-gcp as sub-project of Apache Beam is not a good idea from

Re: [DISCUSS] Externalized Google Cloud Connectors

2024-03-28 Thread Claire McCarthy
Hey Martijn, Apologies, I had missed this message initially! Comments inline. > contributions that have happened outside of the Apache realm do not play a role when evaluating potential new committers. I understand. This, unfortunately, is the tradeoff for developing the connectors outside of Ap

Re: [DISCUSS] Externalized Google Cloud Connectors

2024-03-08 Thread Martijn Visser
Hi Claire, I don't think it's a good idea to actually develop outside of Apache; contributions that have happened outside of the Apache realm do not play a role when evaluating potential new committers. I think the best course of action would be to create a FLIP to add these connectors to the ASF,

Re: [DISCUSS] Externalized Google Cloud Connectors

2024-02-15 Thread Claire McCarthy
Hi Alexander, Thanks so much for the info! It sounds like the best path forward is for us to develop outside of Apache while, in parallel, working to gain committer status. Our goal will be to eventually move anything we build under the Apache umbrella once we're more plugged in to the community.

Re: [DISCUSS] Externalized Google Cloud Connectors

2024-02-14 Thread Alexander Fedulov
Hi Claire, Thanks for reaching out. It's great that there is interest from Google in spearheading the development of the respective Flink connectors. As of now,there is only one GCP-specific connector developed directly as part of ASF Flink, namely the Pub/Sub one. It has already been externalize