Thanks Otto and David - I dont plan to solicit user input as the issue is more of what the developers/maintainers are seeing. For anything we have there is/was at least someone using it. But that has to be matched with someone maintaining it as well. If there are pockets of use/maintenance those can remain on-going but not within the apache project itself until we re-establish critical mass for that standalone kafka connect capability. Given the great work ongoing right now for the Kafka processors I think we keep our focus there.
Will put the PR up. Thanks On Tue, May 7, 2024 at 1:40 PM David Handermann <exceptionfact...@apache.org> wrote: > Joe, > > Thanks for highlighting the Kafka Connect external module. I concur > with your evaluation, I have not observed community usage or > questions, so it seems best to remove from the main branch. > > Regards, > David Handermann > > On Tue, May 7, 2024 at 2:18 PM Otto Fowler <ottobackwa...@gmail.com> > wrote: > > > > I would say nuke it, as you are saying. I would also say you should > cross > > post this to users@ as they will have relevant input > > > > > > On May 7, 2024 at 1:32:11 PM, Joe Witt (joew...@apache.org) wrote: > > > > Team, > > > > The only component remaining is kafka-connect in the nifi-external > module. > > As noted in [1] it does not see much active maintenance and I never see > in > > the apache community any questions/usage related either. Kafka is > > currently on 3.7.0 and this component is Kafka 2.6 for example. > > > > We should not carry this forward in the 2.x line. To be clear Kafka > > remains a super important component to interact with and our Kafka > > components within NiFi do see maintenance including an active PR under > > review right now. But this is our last 'nifi-external' remaining and is > > not maintained. > > > > I'll file a PR under this JIRA [1] and its child JIRA for removal on 2x > and > > deprecation on 1x but wanted to flag this here in case there is some > > substantial usage and/or maintenance/update coming soon. Even if desire > > remains to keep it alive that should be considered to occur in another > repo > > or by another group that leverages it - but please let me know if there > is > > apache community usage/mx I'm not aware of. > > > > Thoughts? > > > > [1] https://issues.apache.org/jira/browse/NIFI-13171 > > > > Thanks > > Joe >
