Eric No it is not meant to run NiFi 1.x components.
You could in theory make 2.x components that happen to have certain 1.x style dependencies but that then is like any other dependency and as a dev you have to fully know what you are selecting. But at a framework level no there is no relationship to nifi 2.x running or being expected to run nifi 1.x components. Thanks On Thu, Dec 12, 2024 at 11:32 PM Eric Secules <esecu...@gmail.com> wrote: > Hi all, > > I am planning an upgrade to NiFi 2.0 and I'm wondering whether NiFi 2.0 is > able to run nars built with dependencies on NiFi 1.27.0 and built on Java > 17? I've confirmed that NiFi is able to start, but I get this warning when > i load my nar into my build from the current head of the main branch and > also the 2.0.0 release tag: > > 2024-12-12 13:38:17,811 WARN [main] org.apache.nifi.nar.NarClassLoaders > While loading '<MY NAR>' unable to locate exact NAR dependency > 'org.apache.nifi:nifi-standard-services-api-nar:1.27.0'. Only found one > possible match > 'org.apache.nifi:nifi-standard-services-api-nar:2.1.0-SNAPSHOT'. > Continuing... > > Is this something to worry about? I've tried > making org.apache.nifi:nifi-standard-services-api-nar:1.27.0 an explicit > dependency of my project but I still get this warning. I even see > "META-INF/bundled-dependencies/nifi-standard-services-api-nar-1.27.0.jar" > when I run jar --list also, I see the jar when I run: > > > find ${NIFI_HOME}/work/nar/extensions/my-nar-1.0.0.nar-unpacked | grep > nifi-standard > ./NAR-INF/bundled-dependencies/nifi-standard-services-api-nar-1.27.0.jar > > I'd like to decouple the NiFi application upgrade from upgrading the build > of my custom processors to support java 21. But I wouldn't want to risk > runtime errors from having to substitute for an incompatible jar. > > Thanks, > Eric > > >