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

Reply via email to