You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@nifi.apache.org by Colin Williams <co...@gmail.com> on 2018/10/19 17:35:49 UTC
Processor not found on loading template. But exists in the
AddProcessor menu.
We've exported a template from a instance running 1.4.0 and also
copied a custom processor nar bundle from this instance. I'd like to
load the template to understand the flow without access to the running
instance we sourced it from.
I get an error that the custom processor is not found, but I see it
from Add Processor menu. Is there a bug in 1.4.0 which might cause
this? Is there another issue regarding exporting and importing
templates in 1.4.0? Can someone suggest a fix for the issue? Also is
there an easy way to enable debugging logs for the binary version?
Thanks,
Colin Williams
Re: Processor not found on loading template. But exists in the
AddProcessor menu.
Posted by Colin Williams <co...@gmail.com>.
After looking at the xml more, it appears some of <processor> tags
which contain the com.comp.cp.nifi.processor.JsonValidateProcessor
have the unversioned bundle and some do not. Then maybe this is the
cause of the issue.
In regards to versioning, the NAR was built for 1.4 and it looks like
the pom is using 1.4 dependencies. I didn't see other deployed nars.
We pulled the NAR off the server, and only saw one custom NAR
deployed. Then I'm not sure regarding the source.
However we removed the processor creating a new template. Then I've
been able to move forward with my own work without this functioning.
Thanks for your help!
On Mon, Oct 22, 2018 at 6:09 AM Bryan Bende <bb...@gmail.com> wrote:
>
> What was the parent element of that "unversioned" bundle?
>
> I think that entry may be the issue, but hard to say how it got there
> since you have other references to the bundle with the correct
> information.
>
> Usually that would occur if you had a NAR that was built before NiFi
> introduced component versioning (I think before 1.2.x) and then you
> deployed that old NAR into 1.2.x or later, it would look for the
> version info in the NAR and not find it and then default the group and
> version to "default" and "unversioned".
>
> On Fri, Oct 19, 2018 at 4:48 PM Colin Williams
> <co...@gmail.com> wrote:
> >
> > Hi Bryan,
> >
> > From the template .xml I see the processor listed in a <type> tag.
> >
> >
> > something like
> >
> > <type>com.comp.cp.nifi.processors.common.JsonValidateProcessor</type>
> >
> > I also see
> >
> > <bundle>
> > <artifact>nifi-cp-bundle-nar</artifact>
> > <group>com.comp.cp.nifi</group>
> > <version>1.0.3</version>
> > </bundle>
> >
> >
> > Then in the UI I see something like
> >
> >
> > Id
> > 8dfb7fb5-0166-1000-65e7-b0080cc28ac1
> > Type
> > JsonValidateProcessor 1.0.3
> > Bundle
> > com.comp.cp.nifi - nifi-cp-bundle-nar
> >
> > It looks pretty similar to me.
> >
> >
> >
> > In the nifi-app.log I see something like:
> >
> > 2018-10-19 13:12:40,705 INFO [main] org.apache.nifi.NiFi Controller
> > initialization took 19191053655 nanoseconds (19 seconds).
> > 2018-10-19 13:12:46,549 INFO [NiFi Web Server-59]
> > c.s.j.s.i.application.WebApplicationImpl Initiating Jersey
> > application, version 'Jersey: 1.19 02/11/2015 03:25 AM'
> > 2018-10-19 13:14:13,740 WARN [NiFi Web Server-18]
> > o.a.nifi.web.StandardNiFiServiceFacade Unable to create Processor of
> > type com.comp.cp.nifi.processor.JsonValidateProcessor to populate
> > default values.
> > 2018-10-19 13:14:13,741 WARN [NiFi Web Server-18]
> > o.a.nifi.web.StandardNiFiServiceFacade Unable to create Processor of
> > type com.comp.cp.nifi.processor.JsonValidateProcessor to populate
> > default values.
> > 2018-10-19 13:14:13,766 INFO [NiFi Web Server-18]
> > o.a.nifi.groups.StandardProcessGroup
> > Template[id=a9075360-984e-4788-922d-1072acbc77c1] added to
> > StandardProcessGroup[identifier=8df558fc-0166-1000-6368-faec63e764af]
> >
> >
> >
> >
> >
> > Also possibly worth mentioning in the template I do see
> >
> > <bundle>
> > <artifact>nifi-cp</artifact>
> > <group>default</group>
> > <version>unversioned</version>
> > </bundle>
> >
> > But I didn't see it referenced from the processor node.
> > On Fri, Oct 19, 2018 at 12:36 PM Colin Williams
> > <co...@gmail.com> wrote:
> > >
> > > Thanks Bryan. I will take a look now. Regarding nifi-app.log, I will
> > > look for it. Wasn't sure if I had to configure something for the
> > > binary version to write the log, or set it's verbosity.
> > > On Fri, Oct 19, 2018 at 12:27 PM Bryan Bende <bb...@gmail.com> wrote:
> > > >
> > > > Can you look in the template using a text editor and find the element
> > > > for the processor you are referring to, and look for the "bundle"
> > > > elements and see if the bundle info (group, artifact, version) in the
> > > > template matches the info for the processor in the UI?
> > > >
> > > > Also would be helpful to see the stacktrace of the error from nifi-app.log
> > > > On Fri, Oct 19, 2018 at 1:36 PM Colin Williams
> > > > <co...@gmail.com> wrote:
> > > > >
> > > > > We've exported a template from a instance running 1.4.0 and also
> > > > > copied a custom processor nar bundle from this instance. I'd like to
> > > > > load the template to understand the flow without access to the running
> > > > > instance we sourced it from.
> > > > >
> > > > > I get an error that the custom processor is not found, but I see it
> > > > > from Add Processor menu. Is there a bug in 1.4.0 which might cause
> > > > > this? Is there another issue regarding exporting and importing
> > > > > templates in 1.4.0? Can someone suggest a fix for the issue? Also is
> > > > > there an easy way to enable debugging logs for the binary version?
> > > > >
> > > > > Thanks,
> > > > >
> > > > > Colin Williams
Re: Processor not found on loading template. But exists in the
AddProcessor menu.
Posted by Bryan Bende <bb...@gmail.com>.
What was the parent element of that "unversioned" bundle?
I think that entry may be the issue, but hard to say how it got there
since you have other references to the bundle with the correct
information.
Usually that would occur if you had a NAR that was built before NiFi
introduced component versioning (I think before 1.2.x) and then you
deployed that old NAR into 1.2.x or later, it would look for the
version info in the NAR and not find it and then default the group and
version to "default" and "unversioned".
On Fri, Oct 19, 2018 at 4:48 PM Colin Williams
<co...@gmail.com> wrote:
>
> Hi Bryan,
>
> From the template .xml I see the processor listed in a <type> tag.
>
>
> something like
>
> <type>com.comp.cp.nifi.processors.common.JsonValidateProcessor</type>
>
> I also see
>
> <bundle>
> <artifact>nifi-cp-bundle-nar</artifact>
> <group>com.comp.cp.nifi</group>
> <version>1.0.3</version>
> </bundle>
>
>
> Then in the UI I see something like
>
>
> Id
> 8dfb7fb5-0166-1000-65e7-b0080cc28ac1
> Type
> JsonValidateProcessor 1.0.3
> Bundle
> com.comp.cp.nifi - nifi-cp-bundle-nar
>
> It looks pretty similar to me.
>
>
>
> In the nifi-app.log I see something like:
>
> 2018-10-19 13:12:40,705 INFO [main] org.apache.nifi.NiFi Controller
> initialization took 19191053655 nanoseconds (19 seconds).
> 2018-10-19 13:12:46,549 INFO [NiFi Web Server-59]
> c.s.j.s.i.application.WebApplicationImpl Initiating Jersey
> application, version 'Jersey: 1.19 02/11/2015 03:25 AM'
> 2018-10-19 13:14:13,740 WARN [NiFi Web Server-18]
> o.a.nifi.web.StandardNiFiServiceFacade Unable to create Processor of
> type com.comp.cp.nifi.processor.JsonValidateProcessor to populate
> default values.
> 2018-10-19 13:14:13,741 WARN [NiFi Web Server-18]
> o.a.nifi.web.StandardNiFiServiceFacade Unable to create Processor of
> type com.comp.cp.nifi.processor.JsonValidateProcessor to populate
> default values.
> 2018-10-19 13:14:13,766 INFO [NiFi Web Server-18]
> o.a.nifi.groups.StandardProcessGroup
> Template[id=a9075360-984e-4788-922d-1072acbc77c1] added to
> StandardProcessGroup[identifier=8df558fc-0166-1000-6368-faec63e764af]
>
>
>
>
>
> Also possibly worth mentioning in the template I do see
>
> <bundle>
> <artifact>nifi-cp</artifact>
> <group>default</group>
> <version>unversioned</version>
> </bundle>
>
> But I didn't see it referenced from the processor node.
> On Fri, Oct 19, 2018 at 12:36 PM Colin Williams
> <co...@gmail.com> wrote:
> >
> > Thanks Bryan. I will take a look now. Regarding nifi-app.log, I will
> > look for it. Wasn't sure if I had to configure something for the
> > binary version to write the log, or set it's verbosity.
> > On Fri, Oct 19, 2018 at 12:27 PM Bryan Bende <bb...@gmail.com> wrote:
> > >
> > > Can you look in the template using a text editor and find the element
> > > for the processor you are referring to, and look for the "bundle"
> > > elements and see if the bundle info (group, artifact, version) in the
> > > template matches the info for the processor in the UI?
> > >
> > > Also would be helpful to see the stacktrace of the error from nifi-app.log
> > > On Fri, Oct 19, 2018 at 1:36 PM Colin Williams
> > > <co...@gmail.com> wrote:
> > > >
> > > > We've exported a template from a instance running 1.4.0 and also
> > > > copied a custom processor nar bundle from this instance. I'd like to
> > > > load the template to understand the flow without access to the running
> > > > instance we sourced it from.
> > > >
> > > > I get an error that the custom processor is not found, but I see it
> > > > from Add Processor menu. Is there a bug in 1.4.0 which might cause
> > > > this? Is there another issue regarding exporting and importing
> > > > templates in 1.4.0? Can someone suggest a fix for the issue? Also is
> > > > there an easy way to enable debugging logs for the binary version?
> > > >
> > > > Thanks,
> > > >
> > > > Colin Williams
Re: Processor not found on loading template. But exists in the
AddProcessor menu.
Posted by Colin Williams <co...@gmail.com>.
Hi Bryan,
From the template .xml I see the processor listed in a <type> tag.
something like
<type>com.comp.cp.nifi.processors.common.JsonValidateProcessor</type>
I also see
<bundle>
<artifact>nifi-cp-bundle-nar</artifact>
<group>com.comp.cp.nifi</group>
<version>1.0.3</version>
</bundle>
Then in the UI I see something like
Id
8dfb7fb5-0166-1000-65e7-b0080cc28ac1
Type
JsonValidateProcessor 1.0.3
Bundle
com.comp.cp.nifi - nifi-cp-bundle-nar
It looks pretty similar to me.
In the nifi-app.log I see something like:
2018-10-19 13:12:40,705 INFO [main] org.apache.nifi.NiFi Controller
initialization took 19191053655 nanoseconds (19 seconds).
2018-10-19 13:12:46,549 INFO [NiFi Web Server-59]
c.s.j.s.i.application.WebApplicationImpl Initiating Jersey
application, version 'Jersey: 1.19 02/11/2015 03:25 AM'
2018-10-19 13:14:13,740 WARN [NiFi Web Server-18]
o.a.nifi.web.StandardNiFiServiceFacade Unable to create Processor of
type com.comp.cp.nifi.processor.JsonValidateProcessor to populate
default values.
2018-10-19 13:14:13,741 WARN [NiFi Web Server-18]
o.a.nifi.web.StandardNiFiServiceFacade Unable to create Processor of
type com.comp.cp.nifi.processor.JsonValidateProcessor to populate
default values.
2018-10-19 13:14:13,766 INFO [NiFi Web Server-18]
o.a.nifi.groups.StandardProcessGroup
Template[id=a9075360-984e-4788-922d-1072acbc77c1] added to
StandardProcessGroup[identifier=8df558fc-0166-1000-6368-faec63e764af]
Also possibly worth mentioning in the template I do see
<bundle>
<artifact>nifi-cp</artifact>
<group>default</group>
<version>unversioned</version>
</bundle>
But I didn't see it referenced from the processor node.
On Fri, Oct 19, 2018 at 12:36 PM Colin Williams
<co...@gmail.com> wrote:
>
> Thanks Bryan. I will take a look now. Regarding nifi-app.log, I will
> look for it. Wasn't sure if I had to configure something for the
> binary version to write the log, or set it's verbosity.
> On Fri, Oct 19, 2018 at 12:27 PM Bryan Bende <bb...@gmail.com> wrote:
> >
> > Can you look in the template using a text editor and find the element
> > for the processor you are referring to, and look for the "bundle"
> > elements and see if the bundle info (group, artifact, version) in the
> > template matches the info for the processor in the UI?
> >
> > Also would be helpful to see the stacktrace of the error from nifi-app.log
> > On Fri, Oct 19, 2018 at 1:36 PM Colin Williams
> > <co...@gmail.com> wrote:
> > >
> > > We've exported a template from a instance running 1.4.0 and also
> > > copied a custom processor nar bundle from this instance. I'd like to
> > > load the template to understand the flow without access to the running
> > > instance we sourced it from.
> > >
> > > I get an error that the custom processor is not found, but I see it
> > > from Add Processor menu. Is there a bug in 1.4.0 which might cause
> > > this? Is there another issue regarding exporting and importing
> > > templates in 1.4.0? Can someone suggest a fix for the issue? Also is
> > > there an easy way to enable debugging logs for the binary version?
> > >
> > > Thanks,
> > >
> > > Colin Williams
Re: Processor not found on loading template. But exists in the
AddProcessor menu.
Posted by Colin Williams <co...@gmail.com>.
Thanks Bryan. I will take a look now. Regarding nifi-app.log, I will
look for it. Wasn't sure if I had to configure something for the
binary version to write the log, or set it's verbosity.
On Fri, Oct 19, 2018 at 12:27 PM Bryan Bende <bb...@gmail.com> wrote:
>
> Can you look in the template using a text editor and find the element
> for the processor you are referring to, and look for the "bundle"
> elements and see if the bundle info (group, artifact, version) in the
> template matches the info for the processor in the UI?
>
> Also would be helpful to see the stacktrace of the error from nifi-app.log
> On Fri, Oct 19, 2018 at 1:36 PM Colin Williams
> <co...@gmail.com> wrote:
> >
> > We've exported a template from a instance running 1.4.0 and also
> > copied a custom processor nar bundle from this instance. I'd like to
> > load the template to understand the flow without access to the running
> > instance we sourced it from.
> >
> > I get an error that the custom processor is not found, but I see it
> > from Add Processor menu. Is there a bug in 1.4.0 which might cause
> > this? Is there another issue regarding exporting and importing
> > templates in 1.4.0? Can someone suggest a fix for the issue? Also is
> > there an easy way to enable debugging logs for the binary version?
> >
> > Thanks,
> >
> > Colin Williams
Re: Processor not found on loading template. But exists in the
AddProcessor menu.
Posted by Bryan Bende <bb...@gmail.com>.
Can you look in the template using a text editor and find the element
for the processor you are referring to, and look for the "bundle"
elements and see if the bundle info (group, artifact, version) in the
template matches the info for the processor in the UI?
Also would be helpful to see the stacktrace of the error from nifi-app.log
On Fri, Oct 19, 2018 at 1:36 PM Colin Williams
<co...@gmail.com> wrote:
>
> We've exported a template from a instance running 1.4.0 and also
> copied a custom processor nar bundle from this instance. I'd like to
> load the template to understand the flow without access to the running
> instance we sourced it from.
>
> I get an error that the custom processor is not found, but I see it
> from Add Processor menu. Is there a bug in 1.4.0 which might cause
> this? Is there another issue regarding exporting and importing
> templates in 1.4.0? Can someone suggest a fix for the issue? Also is
> there an easy way to enable debugging logs for the binary version?
>
> Thanks,
>
> Colin Williams