Hi guys
Thanks again for attention and discussion about my problem. It seems very
common problem and availability of this functionality will simplify not one
NiFI flow =).
>From my humble opinion it would be nice for NiFi to have both approaches,
and proposed by Oleg and proposed Bryan.
I
Devs,
Firstly, I wanted to commend the fantastic product and the great
documentation on the website.
The Contributor's guide and the User Guide is especially good.
I have been going through the code and trying to see if i can contribute on
some of the newbie, beginner Jiras.
As part of doing
Hey Venky,
Welcome to NiFi. Thanks for the compliments on the project but it's thanks to
developers in the community, like yourself, that help develop it that makes it
a great open source project. So again, welcome to NiFi!
As for testing have you seen the testing portion of the devloper's
Venky,
Thanks for putting yourself out to help. The best way is to employ an extensive
testing framework in NiFi. E.g. take a look at
Venky,
You can get a lot out of our mock test framework when creating unit tests.
>From your processor's perspective, this will be the same as running in an
actual NiFi instance.
Also, you can attach a remote debugger by uncommenting the following line
in conf/bootstrap.conf
# Enable Remote
