+1 binding
This is really awesome!
I confirmed hashes and basic usages. Looks great for the 1st release.
Found couple of minor possible improvements on the NiFi side, and
posted comments to NiFi PR2219.
https://github.com/apache/nifi/pull/2219
Thanks for your work and effort, looking forward to
+1
On 2017-12-28 10:09, Bryan Bende wrote:
> Hello,>
>
> I am pleased to be calling this vote for the source release of Apache>
> NiFi Registry 0.1.0.>
>
> The source zip, including signatures, digests, etc. can be found at:>
>
+1, binding
Have been looking forward to this contribution; it is a great addition to
the community!
Following the release helper I verified signatures, hashes as well as
the README,
NOTICE, and LICENSE. Successfully built the project per instructions and
built the NiFi project using the
+1, binding
Awesome stuff and a very welcomed enhancement to the NiFi ecosystem.
Definitely a lot of neat potential to build on from here.
Comments:
hashes and signatures good
build and contrib-check looked good. Had some intermittent issues with NPM
in a clean environment, repeating the build
+1 binding to release this package as nifi-registry-0.1.0
verified sigs, commits, readme.
Ran some basic tests, including validating creating groups, committing
versions, verifying that there was a way to identify that uncommitted
changes existed.
Ensured that my bucket's flow's change
+1, binding
Awesome stuff and a very welcomed enhancement to the NiFi ecosystem.
Definitely a lot of neat potential to build on from here.
Comments:
hashes and signatures good
build and contrib-check looked good. Had some intermittent issues with NPM
in a clean environment, repeating the build
I was thinking that with 16000 processors, you would need a large amount of
heap space allocated to the JVM. A small heap would slow NiFi's ability to
do its work, because the JVM garbage collector would be consuming more CPU
time than what is healthy. A 64 GB heap size, allocated in the NiFi
How many of these 1600 processor groups represent distinct functionality
that cannot be genericized?
Thanks,
Mike
On Thu, Dec 28, 2017 at 8:54 PM, wrote:
> Thanks for your help.
>
> Actually we are using Kylo (https://kylo.io/) which uses NiFi to do the
> work.
>
> There