+1 binding
On Wed, Jan 22, 2020 at 7:44 PM Mark Bean wrote:
> +1, non-binding
>
> checked hashes, built from source, installed and ran simple tests (single
> instance)
> Java 8, MacOS 10.15.2
>
>
>
> On Sun, Jan 19, 2020 at 3:21 PM Joe Witt wrote:
>
> > Hello,
> >
> > I am pleased to be
+1, non-binding
checked hashes, built from source, installed and ran simple tests (single
instance)
Java 8, MacOS 10.15.2
On Sun, Jan 19, 2020 at 3:21 PM Joe Witt wrote:
> Hello,
>
> I am pleased to be calling this vote for the source release of Apache NiFi
> nifi-1.11.0.
>
> The source zip,
+1 (non-binding)
Verified signature/hashes.
Built from source successfully.
Checked the binary release on Java 8 and 11, running some flows including
PutHDFS using native libs.
On Wed, Jan 22, 2020 at 8:19 PM Muazma Zahid wrote:
> +1 (binding)
> Deployed and tested 10 node Cluster in Azure
+1 (binding)
Deployed and tested 10 node Cluster in Azure with the standard flow and
high throughput along with the latest changes in the Azure Reporting task.
On Wed, Jan 22, 2020 at 11:03 AM Nathan Gough wrote:
> +1 non-binding
>
> Verified hashes, signing key, did a 'mvn clean install
>
+1 non-binding
Verified hashes, signing key, did a 'mvn clean install
-Pcontrib-check,include-grpc' and ran a secured NiFi cluster with the
resulting bin.
Nathan
On Wed, Jan 22, 2020 at 11:51 AM Shawn Weeks
wrote:
> +1 non-binding
>
> On 1/22/20, 10:48 AM, "Shawn Weeks" wrote:
>
>
+1 non-binding
On 1/22/20, 10:48 AM, "Shawn Weeks" wrote:
Noticed that the docker compose file
nifi-docker/docker-compose/docker-compose.yml still references
1.10.0-SNAPSHOT-dockermaven in RC3. Not worth holding up for though.
Thanks
Shawn
On 1/22/20, 9:55 AM,
Noticed that the docker compose file
nifi-docker/docker-compose/docker-compose.yml still references
1.10.0-SNAPSHOT-dockermaven in RC3. Not worth holding up for though.
Thanks
Shawn
On 1/22/20, 9:55 AM, "Kevin Doran" wrote:
+1 (binding)
I followed the steps in the release
+1 (binding)
I followed the steps in the release helper guide and verified the signs,
hashes, readme, license, etc.
I was able to performa fun build with tests without any issues on macOS 10.15
(Catalina).
The resulting binary runs well for me running a standard suite of test flows.
One issue
+1 (binding)
Ran through release guide, confirming signatures and hashes. Built with
Java 11 and ran on Mac Os.
Created simple flows on a single node instance and confirmed some of the
latest additions around rules with no issues encountered.
On Wed, Jan 22, 2020 at 9:59 AM Tony Kurc wrote:
>
+1 (binding)
successfully went through the helper guide on mxlinux 18, did not discover
any issues with the signature, hashes, or build.
On Wed, Jan 22, 2020 at 8:48 AM Aldrin Piri wrote:
> +1, binding
>
> comments:
> signature - good
> hashes - good
> L - good
> built and tested some simple
+1, binding
comments:
signature - good
hashes - good
L - good
built and tested some simple flows in conjunction with registry on macos,
debian
thanks for organizing, Joe!
On Wed, Jan 22, 2020 at 8:02 AM Mike Thomsen wrote:
> +1 binding. Ran a flow with a custom processor and verified the fix
+1 binding. Ran a flow with a custom processor and verified the fix for
NIFI-7044.
On Wed, Jan 22, 2020 at 3:15 AM 高橋喜秋 wrote:
> +1 (non-binding)
>
> - [x] Non-RPM (usual) build with Java 8.
> - [x] Deploy on 3 node secured cluster in CentOS 7.7.0 and run on Java 8.
> - [x] Non-RPM (usual)
+1 (non-binding)
- [x] Non-RPM (usual) build with Java 8.
- [x] Deploy on 3 node secured cluster in CentOS 7.7.0 and run on Java 8.
- [x] Non-RPM (usual) build with Java 11.
- [x] Deploy on 1 node non secured cluster in CentOS 7.7.0 and run on Java 11.
Thanks for working for the release!
On
+1 (binding)
Ran through helper guide for validation.
Built on pop os and osx.
Ran a high throughout test flow, where I encountered no regressions across
several record oriented processors and non secure site to site.
Thanks,
Marc
On Tue, Jan 21, 2020, 4:43 PM Andrew Lim wrote:
> +1
+1 (non-binding)
-Ran full clean install on OS X (Catalina 10.15.2)
-Tested secure NiFi with secure NiFi Registry
-Ran basic flows successfully
-Reviewed core UI and documentation fixes/updates
In setting up my secure NiFi and secure NiFi registry, I used the NiFi TLS
Toolkit [1] to create my
+1 (binding)
Ran through release helper, tried various flows including some new
features (PutRecord, e.g.) PutRecord might not have made the
improvements list, changelog, release notes, etc. for 1.11 due to an
omission in Jira, but the Jira has since been corrected [1]
-Matt
[1]
+1
- Deploy on 3 node cluster in Azure
- Ran test data flow with high throughput
- Verified new changes in RC3
Looks good! Nice work everyone
On Tue, Jan 21, 2020 at 6:11 AM Arpad Boda wrote:
> +1
>
>- Verified signature, checksums.
>- Built properly.
>- Started NiFi, sent
+1
- Verified signature, checksums.
- Built properly.
- Started NiFi, sent flowfiles from MiNiFi, designed flow to handle
them.
Created https://issues.apache.org/jira/browse/NIFI-7049 in the meanwhile as:
- SFTP tests can fail on "clean" hosts
- The underlying behavior seems
+1 (binding) release this package as nifi-1.11.0
Went through the usual check process. Also deployed a 3-nodes secured
cluster with OIDC behind a load balancer with Terraform on Google Cloud.
Tested various flows. It looks good to me.
Some notes - I did run into a test failure (that I didn't
Hello,
I am pleased to be calling this vote for the source release of Apache NiFi
nifi-1.11.0.
The source zip, including signatures, digests, etc. can be found at:
https://repository.apache.org/content/repositories/orgapachenifi-1155
The source being voted upon and the convenience binaries can
20 matches
Mail list logo
