Andy,
Profuse thanks for the time spent on this. I did not invent this
simplified project structure, but stumbled upon it and tried it out
adding it to these notes when I discovered that it worked (trivially at
least since the processor works, but as we know the documentation bit
doesn't
Russ,
I don’t know where the idea to do a “single-module project” came from. The
recommended (read: working) method is to have multiple Maven modules — a parent
(usually called “nifi-myprocessor-bundle”), a processor
(“nifi-myprocessor-processor”), and a NAR builder (“nifi-myprocessor-nar”).
Thanks, Andy, no offense taken. I tried this in Chrome and Firefox, but
am still getting that default page. My sample flow also contains an
instance of GetFile feeding sample files into CustomProcessor. When I
look at GetFile's usage, I see /Description: Creates FlowFiles from file
in a
Hi Russ,
I hate to suggest something so simple, but have you cleared the cache of your
browser? Sometimes this can be a result of stale caching.
Andy LoPresto
alopre...@apache.org
alopresto.apa...@gmail.com
PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4 BACE 3C6E F65B 2F7D EF69
> On Jan 27,
Addendum: the @TagsI add are not showing up in the tag field at the
left, but when I scroll down in the processor list and see my new custom
processor, I do see these tags listed next, to its right.
On 1/27/20 3:27 PM, Russell Bateman wrote:
Perhaps I made my question less clear that I could
Perhaps I made my question less clear that I could have. Consider that I
have this annotation on the class of processor:
@CapabilityDescription( "Custom processor usage statement..." )
and, because my processor is listed in the file
My custom processor's usage, which should come from the
@CapabilityDescription annotation of the class containing the
onTrigger() method, nevertheless is nothing more than the Apache NiFi
Overview. I am able to place an instance on the canvas via the processor
Component Tool (so, the custom
