After looking at the xml more, it appears some of 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
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
Hi Bryan,
>From the template .xml I see the processor listed in a tag.
something like
com.comp.cp.nifi.processors.common.JsonValidateProcessor
I also see
nifi-cp-bundle-nar
com.comp.cp.nifi
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 wrote:
>
> Can you look in the template using a text editor
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
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
