Hi Mike and Bryan, One of my custom processors appears as inactive in NiFi with a yellow triangle error. When I hover over it I see a message saying 'Missing Processor' validated against 'Any Property' is invalid. This is not a valid processor. In the log it seems to invoke GhostProcessor.java which is giving the above error when restarting nifi. This custom processor sits (with my other processors) in my custom_lib folder and I have provided that path in the nifi properties file as
*nifi.nar.library.directory.custom=/opt/nifi/custom_lib* Not sure what I missed? Do I need to make entry of this custom processor somewhere? On Thu, Aug 8, 2019 at 9:14 AM Bimal Mehta <bimal...@gmail.com> wrote: > Thanks Mike and Bryan. > Yes it seems my template was still referring the old version. > I will have it updated now and will reimport. > Also the version of NiFi we are using is the one that comes with CDF. I am > not sure if CDF supports 1.9.2 yet or not. I will reach out to Cloudera and > see if we can get it upgraded. > > > > On Thu, Aug 8, 2019, 8:51 AM Bryan Bende <bbe...@gmail.com> wrote: > >> What is in the template for the bundle coordinates of your processor? >> and does that match the coordinates of the NAR that is deployed? >> >> Example: >> >> <bundle> >> <group>org.apache.nifi</group> >> <artifact>nifi-update-attribute-nar</artifact> >> <version>1.10.0-SNAPSHOT</version> >> </bundle> >> >> If you made a new version of your NAR, say 2.0.0 and your template >> references 1.0.0, then you'll need to update your template. >> >> On Wed, Aug 7, 2019 at 10:05 PM Mike Thomsen <mikerthom...@gmail.com> >> wrote: >> > >> > If it's happening immediately upon trying to import the template, I >> believe that's the error message saying that the 1.9 instance cannot find >> the NAR file which provided the processor. Also, if you're referring to >> 1.9.0 and not 1.9.2 you're going to want to upgrade to the latter because >> there are a few critical bugs fixed in 1.9.2. >> > >> > On Wed, Aug 7, 2019 at 9:19 PM Bimal Mehta <bimal...@gmail.com> wrote: >> >> >> >> Thanks Bryan. >> >> My custom processors are part of a template. However when I try to >> import my template in NiFi 1.9, I get an error message saying >> >> PutFeedMetadata is not known to this NiFi instance. I did update all >> the dependencies to NiFi 1.9 and even the plugins. We are using a Cloudera >> distributed version of NiFi 1.9. >> >> Any idea why is this happening? >> >> >> >> Thanks >> >> >> >> >> >> >> >> On Wed, Aug 7, 2019 at 3:46 PM Bryan Bende <bbe...@gmail.com> wrote: >> >>> >> >>> Hello, >> >>> >> >>> Most likely your processor built against 1.6 would run fine in 1.9, >> >>> but to make sure you just need to update any nifi dependencies in your >> >>> poms to 1.9.2. >> >>> >> >>> If you created your project from the archetype and didn't change >> >>> anything, then this should just be changing the parent in the root pom >> >>> to the new version of nifi-nar-bundles. >> >>> >> >>> If you set it up yourself, then anywhere you depend on nifi-api you >> >>> need to change. >> >>> >> >>> -Bryan >> >>> >> >>> On Wed, Aug 7, 2019 at 3:18 PM Bimal Mehta <bimal...@gmail.com> >> wrote: >> >>> > >> >>> > Hi, >> >>> > >> >>> > If we have a custom processor that was created with NiFi 1.6, what >> are the steps we need to follow to make it work in 1.9? >> >>> > Is there some sort of steps that explains the jar and pom updates >> we need to do for making it work in 1.9? >> >