+1 (non-binding)
Verified signatures, checksums, LICENSE and NOTICE
Build was successful on OS X (JDK 1.8.0_111-b14)
Tested basic flows in standalone and three node cluster (using GetTwitter,
JoltTransformJson, PutMongo)
Tested upgrade use case of moving from 1.0.0 to 1.1.0 (See Andre's email
+1 from me. Built without issue for me on Windows 10 and Ubuntu 14.04
(x86_64). My sample flows ran without issue. Did not spot any issues with
licenses. Signature and hashes verified.
On Nov 27, 2016 8:32 PM, "Koji Kawamura" wrote:
> +1 (non-binding)
>
> - Verified
+1 (non-binding)
- Verified checksums
- Successfully ran mvn clean install, on OS X and Windows Server 2016,
with Oracle JDK 1.8.0_111-b14, mvn 3.3.9
- Run example data flows on OS X and Windows
Building and testing on Windows went well without issue. I hope the
InvokeScriptedProcessor test
Aldrin,
I saw the same exception on that test on OS X but it resolved when I
upgraded my version of java (upgraded to 1.8.0_111-b14)
On Sun, Nov 27, 2016 at 5:13 PM, Aldrin Piri wrote:
> +1, binding
>
> Hashes and signatures looked good.
> Contrib passed
> Builds and
Odd, I am still verifying the release, but I was able to build without
issue on Windows 10. Using Oracle java 1.8.0_91 and Apache maven 3.3.3
On Nov 27, 2016 5:14 PM, "Aldrin Piri" wrote:
> +1, binding
>
> Hashes and signatures looked good.
> Contrib passed
> Builds and
+1, binding
Hashes and signatures looked good.
Contrib passed
Builds and functionality were okay on OS X and Linux.
I could not get a successful build on Windows 10 without removing some
tests. I ran into the item covered in
https://issues.apache.org/jira/browse/NIFI-2692 from the 1.0 release