Awesome Chris and David - both of those are done and dusted! Amazing. Matt; Thanks yes for Hive it should just be simplifying/updating the Iceberg dependency on Hive to the latest or even removing if not necessary. Iceberg itself can be updated but my understanding is the 1.5.1 release has a problem and there will soon be a 1.5.2 we should wait for (someone else had a PR for that and backed it out for now). The flyway one is hopefully easy similar to the QuestDB one.
We have some other dependencies in need to attention which I've not created JIRAs for: 1. Mongo DB. We're on 4.11 and the latest is 5.1 2. SNMP4J. We're on 2.8/2.7 and the latest are 3.8 for the primary lib and agent. 3. Redis. We're on 3.10 and the latest is 5.1 4. Camel Salesforce Lib. We're on 3.14 and the latest is 4.5 5. Fastcsv. We're on 2.2.2 and the latest is 3.1.0 There are a handful of others but these are the top of mind ones in scanning the results. For those wanting to see this list on your own in the root of nifi.git run: mvn -T 1.0C versions:dependency-updates-aggregate-report -DonlyUpgradable=true Then open target/site/dependency-updates-aggregate-report.html Thanks Joe On Tue, May 7, 2024 at 2:05 PM David Handermann <exceptionfact...@apache.org> wrote: > Joe, > > Thanks for highlighting these areas to be updated. I was able to > address the QuestDB update with a couple minor adjustments, and > submitted a PR [1]. > > Regards, > David Handermann > > [1] https://github.com/apache/nifi/pull/8773 > > On Tue, May 7, 2024 at 2:58 PM Chris Sampson > <chris.samp...@naimuri.com.invalid> wrote: > > > > I’ll pick up the Elasticsearch dependency upgrade. > > > > I’ll try to test it again OpenSearch as well, if for no reason other > than to prove either way whether the current NiFi components will work with > the AWS service, although I may not get to do that and instead testing will > focus on Elasticsearch 8.x instances (and the existing Integration Tests > within NiFi). > > > > > > Cheers, > > > > --- > > Chris Sampson > > IT Consultant > > chris.samp...@naimuri.com > > > > > > > On 7 May 2024, at 20:54, Joe Witt <joe.w...@gmail.com> wrote: > > > > > > Yeah sorry - what I wrote for the Hive one was a bit nonsensical. I > tried > > > to clarify it better in the JIRA. > > > > > > Thanks > > > > > > On Tue, May 7, 2024 at 12:38 PM Matt Burgess <mattyb...@gmail.com> > wrote: > > > > > >> For [1] Hive 3 was removed in > > >> https://issues.apache.org/jira/browse/NIFI-12981, if you mean the > Hive > > >> dependency from Apache Iceberg we probably need a release from them > that > > >> brings in Hive 4 dependencies? Or do you suggest we bring the Hive > > >> components back as long as we update the version? > > >> > > >> I'll take the Flyway one in the meantime, database integrations are my > > >> blessing and my curse :) If that goes more smoothly than I expect I > can > > >> grab the QuestDB one too, will update the Jiras as appropriate. > > >> > > >> Regards, > > >> Matt > > >> > > >> On Tue, May 7, 2024 at 1:56 PM Joe Witt <joew...@apache.org> wrote: > > >> > > >>> Team, > > >>> > > >>> We have made massive strides going from thousands of out of date > > >> libraries > > >>> to dozens in the 2.x line vs any prior releases. And we can/should > stay > > >> on > > >>> top of these better going forward. A few key bits that are > outstanding > > >>> with no obvious immediate work underway are as follows. If anyone is > > >>> working on these, willing to work on these, please volunteer and let > us > > >>> know. For components that we cannot find active engagement on we > should > > >>> consider removal though these aren't great examples as they're indeed > > >>> common usage components. > > >>> > > >>> [1] https://issues.apache.org/jira/browse/NIFI-13173 > > >>> Hive 4 recently came out but Hive also gives us some of the most > > >>> complicated POM/library mangling and oldest dependencies to > > >> override/etc.. > > >>> Putting serious detailed focus here is very valuable from a > maintenance > > >>> point of view. While existing usage of Hive 3 likely remains for > some > > >>> time, those users are like NiFi 1.x users anyway. In any case if > there > > >> are > > >>> motivated developers interested to see our Hive components be healthy > > >>> please do dive in on this. > > >>> > > >>> [2] https://issues.apache.org/jira/browse/NIFI-13169 > > >>> The NiFI registry is a major release behind Flyway DB. We need to > stay > > >>> current given the importance of this component. > > >>> > > >>> [3] https://issues.apache.org/jira/browse/NIFI-13168 > > >>> We are a few incrementals behind and a minor release behind > QuestDB. I > > >>> tried bumping the incremental but it broke tests. > > >>> > > >>> [4] https://issues.apache.org/jira/browse/NIFI-11686 > > >>> We are a full major release behind and several incremental/minors as > > >> well. > > >>> Apparently there is some concern related to the community changes in > > >>> Elastic vs OpenSearch/etc.. but regardless we need to stay active in > > >>> maintaining this component. We really should get to the latest main. > > >>> > > >>> Thanks to anyone who can help tackle these and make progress both in > > >> terms > > >>> of doing the upgrade/update work, validating tests, fixing licenses, > but > > >>> also reviews. > > >>> > > >>> Thanks > > >>> Joe > > >>> > > >> > > >
