Apache NiFi Community,
I am pleased to announce that the 1.3.0 release of Apache NiFi passes with
12 +1 (binding) votes
7 +1 (non-binding) votes
0 0 votes
0 -1 votes
Thanks to all who helped make this release possible.
Here is the PMC vote thread:
+1 (non-binding)
Build looks good, ran some sample flows that executed as expected.
On Wed, Jun 7, 2017 at 3:06 PM Bryan Rosander wrote:
> +1 (non-binding)
>
> Verified signature, hashes
> contrib-check build with fresh m2 folder
> simple flow testing s2s from MiNiFi Java
+1 (non-binding)
Verified signature, hashes
contrib-check build with fresh m2 folder
simple flow testing s2s from MiNiFi Java and C++ to secured and unsecured
nifi clusters
On Wed, Jun 7, 2017 at 12:48 PM, Kevin Doran
wrote:
> +1 (non-binding), release this package as
+1 (non-binding), release this package as nifi-1.3.0
Verified hash, tag.
Full contrib-check build.
Ran a simple site-to-site test and was able to send flow files.
On 6/5/17, 13:54, "Matt Gilman" wrote:
Hello,
I am pleased to be calling this vote for the
+1 (binding), verified hash, tag, full build with tests and
contrib-check, ran some record-related flows and random test flows
On Mon, Jun 5, 2017 at 1:54 PM, Matt Gilman wrote:
> Hello,
>
>
> I am pleased to be calling this vote for the source release of Apache NiFi
>
+1 (non-binding)
-Ran full clean install on OS X (10.11.4)
-Tested UI changes
-Tested flows using CaptureChangeMySQL, PutDatabaseRecord processors and
controller services, working as expected
> On Jun 5, 2017, at 1:54 PM, Matt Gilman wrote:
>
> Hello,
>
>
> I am
+1 (binding) Release this package as nifi-1.3.0
On Mon, Jun 5, 2017 at 1:54 PM, Matt Gilman wrote:
> Hello,
>
>
> I am pleased to be calling this vote for the source release of Apache NiFi
> nifi-1.3.0.
>
>
> The source zip, including signatures, digests, etc. can be found
+1 binding
On Wed, Jun 7, 2017 at 1:08 PM, Aldrin Piri wrote:
> +1, binding
>
> Hashes and signature looks good
> Build and contrib check was clean
> README, L look good
> Verified some simple flows
>
>
> Environment:
> Apache Maven 3.3.1
+1 ( non binding )
Verified checksums and hashes
Verified build on Linux (ubuntu 16.0.4)
Verified simple flows, one of which used minifi as a source.
On Jun 7, 2017 4:13 AM, "Joey Frazee" wrote:
+1 (non-binding)
- Verified checksums, signatures and commit ID
-
+1 (non-binding)
- Verified checksums, signatures and commit ID
- Successfully built and ran tests on OSX, Amazon Linux, and Docker maven:latest
- Built RPM with `mvn -T 2.0C clean install -Prpm,generateArchives -DskipTests`
and tested install
- Tested data flows with ConvertRecord and
+1, binding
Hashes and signature looks good
Build and contrib check was clean
README, L look good
Verified some simple flows
Environment:
Apache Maven 3.3.1 (cab6659f9874fa96462afef40fcf6bc033d58c1c;
2015-03-13T16:10:27-04:00)
Maven home: /usr/local/maven
Java version: 1.8.0_121, vendor: Oracle
+1 (binding)
- ran through release helper
- ran clean build, test passed without issue
- ran simple flow using standalone/non-secure/secure/clustered NiFi
- confirmed few JIRAs data flow those had been addressed within 1.3.0
On Wed, Jun 7, 2017 at 2:15 AM, Pierre Villard
+1 (binding)
- verified signatures, checksums, license, notice and readme.
- full build on OSX, Windows 10, CentOS 7 (faced some test errors while
building on Windows but the failing tests have already opened JIRAs to
track them)
- checked UIs changes
- tested some workflows for Record based
+1 (non-binding)
- Verified signatures, checksums, LICENSE, NOTICE, and README
- Built using a full clean build with contrib check successfully on OSX
- Run example data flows on OS X with Chrome Version 58.0.3029.110 (64-bit)
on unsecured instance
- Run example data flows on OS X with Chrome
+1 (binding)
* Verified GPG signature.
* Verified hashes.
* Built source with contrib-check profile.
* Verified README, NOTICE, and LICENSE.
* Verified commit ID.
* Verified RC was branched from master.
* Ran binary and tested basic functionality.
On Tue, Jun 6, 2017 at 10:27 AM, Bryan Bende
+1 (binding) Release this package as nifi-1.3.0
- Ran through release helper and everything checked out
- Ran some test flows with HDFS processors and verified they worked correctly
On Tue, Jun 6, 2017 at 12:42 AM, James Wing wrote:
> +1 (binding). I ran through the release
+1 (binding). I ran through the release helper -- verified signature and
hashes, ran the full build, checked readme, license, and notice in source
and output. I ran a simple flow and verified that it still works.
Thanks for putting this release together, Matt.
James
On Mon, Jun 5, 2017 at
+1 (binding)
Full build w/contrib check passes. All hashes, signature, commit hash
looks good. Binary and source L checks out. Manually testing was
favorable. Did find trouble when opting in to the new provenance
writeahead repo and filed [1].
[1]
I was incorrect in my notes below: the lookup was only introduced post-1.2.0. I
meant that the imported flow worked in an earlier version of 1.3.0-SNAPSHOT and
I had to make adjustments to be compatible with the release candidate. There is
no concern for people upgrading from 1.2.0.
Andy
+1 (binding)
I downloaded the artifacts, verified the signature and hashes, built the app
(with all tests and contrib-check passing), and ran it with a flow that worked
in 1.2.0 performing scripted record lookups using a controller service. At
first this failed because the API has changed, so
Filed https://issues.apache.org/jira/browse/NIFI-4021
And PullRequest https://github.com/apache/nifi/pull/1892
On Tue, Jun 6, 2017 at 10:54 AM, Koji Kawamura wrote:
> Hi Adam, Jeff,
>
> StandardFlowSynchronizerSpec relies on System.property so it can pass
> if other test
Hi Adam, Jeff,
StandardFlowSynchronizerSpec relies on System.property so it can pass
if other test sets 'nifi.properties.file.path'.
I think I found how to fix the test class. I will create a JIRA and
send a PR for it.
Thanks,
Koji
On Tue, Jun 6, 2017 at 9:35 AM, Jeff wrote:
Hi Adam,
StandardFlowSynchronizerSpec via command line maven on my MBP passes
successfully, but I do see the same errors as you when running the tests
for StandardFlowSynchronizerSpec through IntelliJ.
On Mon, Jun 5, 2017 at 6:56 PM Adam Taft wrote:
> Got past the first
Got past the first error, thanks Joey. Indeed, the non-root user was the
fix.
Unfortunately, now I'm getting another test failure. Can anyone confirm
this one?
Running org.apache.nifi.controller.StandardFlowSynchronizerSpec
Tests run: 4, Failures: 0, Errors: 4, Skipped: 0, Time elapsed: 0.677
OK, will check out root/non-root. Thanks for the heads up on that. Give
me a minute, will check with a non-root user.
Adam
On Mon, Jun 5, 2017 at 4:12 PM, Joey Frazee wrote:
> Adam, this can happen if you're building as root (E.g., if you're being
> lazy like me and
Adam,
Thanks for the heads up on the missing tag. When I pushed up the release
branch I had forgotten to include the tags. It should be there now. Sorry
about that.
I did not have any trouble with the test you specified. Is it sporadic or
does it fail every time? That test appears unchanged
I'm getting a test failure for this RC. Here is the maven snippet.
---
T E S T S
---
Running org.apache.nifi.provenance.CryptoUtilsTest
Tests run: 16, Failures: 1, Errors: 0, Skipped: 0, Time
Hello,
I am pleased to be calling this vote for the source release of Apache NiFi
nifi-1.3.0.
The source zip, including signatures, digests, etc. can be found at:
https://repository.apache.org/content/repositories/orgapachenifi-1108
The Git tag is nifi-1.3.0-RC1
The Git commit ID is
28 matches
Mail list logo