Hi, According to the current standards I created a Google doc for the FLIP [1]. I pointed it to the this discussion but if a dedicated discussion should be started for it, pls. let me know. PTAL.
Regards, Ferenc [1] https://docs.google.com/document/d/1vHF_uVe0FTYCb6PRVStovqDeqb_C_FKjt2P5xXa7uhE/edit On Thursday, February 29th, 2024 at 09:48, Ferenc Csaky <ferenc.cs...@pm.me.INVALID> wrote: > > > Thank you Marton and Martijn, I will proceed with the FLIP then. > > Best, > Ferenc > > > > > On Wednesday, February 28th, 2024 at 21:15, Martijn Visser > martijnvis...@apache.org wrote: > > > Hi all, > > > > +1 to have a connector FLIP to propose a Kudu connector. I'm +0 overall > > because I don't see a lot of activity happening in newly proposed > > connectors, but if there's demand for it and people want to volunteer with > > contributions, there's no reason to block it. > > > > Best regards, > > > > Martijn > > > > On Wed, Feb 28, 2024 at 4:31 PM Márton Balassi balassi.mar...@gmail.com > > > > wrote: > > > > > Hi team, > > > > > > Thanks for bringing this up, Feri. I am +1 for maintaining the Kudu > > > connector as an external Flink connector. > > > > > > As per the legal/trademark questions this is actually fair game because > > > one > > > does not donate code to a specific Apache project, technically it is > > > donated to the Apache Software foundation. Consequently moving between ASF > > > projects is fine, I would add a line to the NOTICE file stating that this > > > code originally lived in Bahir once we forked it. > > > > > > Although I did not find an easy to link precedent this is also implied in > > > the Attic Bahir site [1] ("notify us if you fork outside Apache") and in > > > this [2] Apache community dev list chat. We should notify the Attic team > > > in > > > any case. :-) > > > > > > [1] https://attic.apache.org/projects/bahir.html > > > [2] https://lists.apache.org/thread/p31mz4x4dcvd43f026d5p05rpglzfyrt > > > > > > On Tue, Feb 27, 2024 at 10:09 AM Ferenc Csaky ferenc.cs...@pm.me.invalid > > > wrote: > > > > > > > Thank you Leonard for sharing your thoughts on this topic. > > > > > > > > I agree that complying with the Flink community connector > > > > development process would be a must, if there are no legal or > > > > copyright issues, I would be happy to take that task for this > > > > particular case. > > > > > > > > I am no legal/copyright expert myslef, but Bahir uses the Apache > > > > 2.0 license as well, so I believe it should be possible without too many > > > > complications, but I try to look for help on that front. > > > > > > > > FYI we are using and supporting a downstream fork of the Kudu connector > > > > on > > > > top of Flink 1.18 without any major modifications, so it is pretty up to > > > > date upstream as well. > > > > > > > > Regards, > > > > Ferenc > > > > > > > > On Monday, February 26th, 2024 at 10:29, Leonard Xu xbjt...@gmail.com > > > > wrote: > > > > > > > > > Hey, Ferenc > > > > > > > > > > Thanks for initiating this discussion. Apache Bahir is a great project > > > > > that provided significant assistance to many Apache Flink/Spark users. > > > > > It's > > > > > pity news that it has been retired. > > > > > > > > > > I believe that connectivity is crucial for building the ecosystem of > > > > > the > > > > > Flink such a computing engine. The community, or at least I, would > > > > > actively > > > > > support the introduction and maintenance of new connectors. Therefore, > > > > > adding a Kudu connector or other connectors from Bahir makes sense to > > > > > me, > > > > > as long as we adhere to the development process for connectors in the > > > > > Flink > > > > > community[1]. > > > > > I recently visited the Bahir Flink repository. Although the last > > > > > release > > > > > of Bahir Flink was in August ’22[2] which is compatible with Flink > > > > > 1.14, > > > > > its latest code is compatible with Flink 1.17[3]. So, based on the > > > > > existing > > > > > codebase, developing an official Apache Flink connector for Kudu or > > > > > other > > > > > connectors should be manageable. One point to consider is that if > > > > > we're > > > > > not > > > > > developing a connector entirely from scratch but based on an existing > > > > > repository, we must ensure that there are no copyright issues. Here, > > > > > "no > > > > > issues" means satisfying both Apache Bahir's and Apache Flink's > > > > > copyright > > > > > requirements. Honestly, I'm not an expert in copyright or legal > > > > > matters. > > > > > If > > > > > you're interested in contributing to the Kudu connector, it might be > > > > > necessary to attract other experienced community members to > > > > > participate > > > > > in > > > > > this aspect. > > > > > > > > > > Best, > > > > > Leonard > > > > > > > > > > [1] > > > > > > https://cwiki.apache.org/confluence/display/FLINK/FLIP+Connector+Template > > > > > > > > [2] https://github.com/apache/bahir-flink/releases/tag/v1.1.0 > > > > > [3] https://github.com/apache/bahir-flink/blob/master/pom.xml#L116 > > > > > > > > > > > 2024年2月22日 下午6:37，Ferenc Csaky ferenc.cs...@pm.me.INVALID 写道： > > > > > > > > > > > > Hello devs, > > > > > > > > > > > > Just saw that the Bahir project is retired [1]. Any plans on what's > > > > > > happening with the Flink connectors that were part of this project? > > > > > > We > > > > > > specifically use the Kudu connector and integrate it to our > > > > > > platform at > > > > > > Cloudera, so we would be okay to maintain it. Would it be possible > > > > > > to > > > > > > carry > > > > > > it over as separate connector repu under the Apache umbrella > > > > > > similarly as > > > > > > it happened with the external connectors previously? > > > > > > > > > > > > Thanks, > > > > > > Ferenc
