Hey Joe,
I've seen this error crop up a time or two before. The issue is a bug in how we
are handling a failure
condition. Haven't yet figured out the best way to tackle it, but the thing to
note is that this error occurs
when there is some other sort of failure -- typically, a failure to
Apache NiFi Community,
I am pleased to announce that the 1.4.0 release of Apache NiFi passes with
10 +1 (binding) votes
9 +1 (non-binding) votes
1 0 votes
0 -1 votes
Thanks to all who helped make this release possible.
Here is the PMC vote thread:
I have to change my non-binding +1 vote to a 0, unless there is a
workaround for the bug [1] I just submitted, regarding the QueryRecord
processor being broken.
[1] https://issues.apache.org/jira/browse/NIFI-4452
On Mon, Oct 2, 2017 at 3:23 AM, Kevin Doran wrote:
>
+1, non-binding
- Verified hashes
- Full build with contrib-check passes
- Was able to run nifi server and send flow files to remote input port over s2s
protocol. Web UI and API working as expected.
Platform:
Apache Maven 3.5.0 (ff8f5e7444045639af65f6095c62210b5713f426;
+1 (non-binding).
Upgraded to 1.4.0, openJDK 1.8.0_102, RHEL. No issues.
-Original Message-
From: Joey Frazee [mailto:joey.fra...@icloud.com]
Sent: Monday, October 02, 2017 3:50 AM
To: dev@nifi.apache.org
Subject: [EXT] Re: [VOTE] Release Apache NiFi 1.4.0 (RC2)
+1 (non-binding
+1 (non-binding)
- Verified checksums and signature
- Successfully built and ran tests on OSX (Oracle 1.8.0_131), Amazon Linux
(Oracle 1.8.0_131), and Docker maven:latest (OpenJDK 1.8.0_141)
- Built RPM with `mvn -T 2.0C clean install -Prpm,generateArchives -DskipTests`
and tested install
-
+1 (non-binding)
Built on CentOS 7, upgraded an existing 1.3.0 cluster, ran a complex flow
with self-RPGs, reporting tasks, and controller services. All looks good!
The Avro viewer is especially nice, and the double-click feature already
feels natural. Great work!
On Sun, Oct 1, 2017 at 4:41
+1 (binding)
Built on OSX 10.12.5 and Windows 8.1, and ran very simple flows on OSX,
Windows 8.1 and Windows 10. When building on Windows 8.1, ran into previous
test failures and a couple new ones found here[1]. As stated before, not
important enough to downvote the release.
Also one thing to
+1 (binding)
Did all the normal release validation/L/sigs/etc..
Did a bunch of different tests largely focused on high performance and
stability. Things look really good.
I did run into a test failure which I've narrowed down to the latest
JRE/JDK version. Details
Verified hash, local build was successful on OS X, confirmed!
Good Version!
On Sat, 30 Sep 2017 at 09:32 Tony Kurc wrote:
> +1 (binding)
>
> Built on Ubuntu 14.04 with Java 1.8.0 and Maven 3.5.0. Verified hashes and
> signature. Tested some simple flows. Tested some tls
+1 (binding)
Built on Ubuntu 14.04 with Java 1.8.0 and Maven 3.5.0. Verified hashes and
signature. Tested some simple flows. Tested some tls toolkit operations.
Did not see any issues with LICENSE or NOTICE files.
On Sat, Sep 30, 2017 at 4:17 AM, Koji Kawamura
wrote:
>
+1 (binding) Release this package as nifi-1.4.0
Verified hashes, local build was successful on OS X, confirmed S2S
communication with older versions.
On Sat, Sep 30, 2017 at 9:27 AM, Andy LoPresto wrote:
> +1 (binding)
>
> Build environment: Mac OS X 10.11.6, Java
+1 (binding)
Build environment: Mac OS X 10.11.6, Java 1.8.0_101, Maven 3.3.9, JCE Unlimited
Strength Cryptographic Jurisdiction Policies installed
* verified GPG signature is valid and SHA512 digest
* verified all checksums
* verified all tests
* verified checkstyle
* verified Knox properties
+1 (non-binding)
-Ran full clean install on OS X (10.11.4)
-Tested UI changes including Variable Registry UI
-Tested flows using Record reader/writer processors and controller services,
working as expected
> On Sep 29, 2017, at 4:50 PM, Michael Moser wrote:
>
> +1
+1 (non-binding)
Verified source package per release helper.
Built on Ubuntu 14.04, all unit tests and contrib-check pass.
Built on Windows 10, some unit tests fail and contrib-check fails on
"nifi-poi-processors: Too many files with unapproved license" but I
think this was expected. The build
+1 (non-binding) Release this package as nifi-1.4.0
On Fri, Sep 29, 2017 at 11:52 AM, Mark Payne wrote:
> +1 (binding)
>
> Verified hashes and checksum. Built with all unit tests and contrib-check
> on OSX.
>
> Was able to startup and test simple flows worked as expected.
+1 non-binding
-- verified contrib-check
-- ran simple flows with MiNiFi
-- sigs and hashes look good.
Thanks for sending this out Jeff!
On Fri, Sep 29, 2017 at 11:18 AM, Matt Gilman
wrote:
> +1 (binding) Release this package as nifi-1.4.0
>
> On Fri, Sep 29,
+1 (binding) Release this package as nifi-1.4.0
On Fri, Sep 29, 2017 at 11:07 AM, Bryan Bende wrote:
> +1 (binding)
>
> - Ran through the release helper and everything checked out.
> - Ran a couple of sample flows with no issues
>
>
> On Fri, Sep 29, 2017 at 9:46 AM, James
+1 (binding)
- Ran through the release helper and everything checked out.
- Ran a couple of sample flows with no issues
On Fri, Sep 29, 2017 at 9:46 AM, James Wing wrote:
> Jeff, I agree the updated KEYS file has been published. Thanks.
>
> On Fri, Sep 29, 2017 at 6:00 AM,
Jeff, I agree the updated KEYS file has been published. Thanks.
On Fri, Sep 29, 2017 at 6:00 AM, Jeff wrote:
> James,
>
> I had to do a hard reload of the page in Chrome, since the browser kept
> showing me a cached version without my key. After the hard reload, I can
> see
+1, binding
Notes:
* Hashes and signature looked good
* No binaries
* Release matches source commit
* Build with contrib check passes
* Running some simple flows looks good
On Fri, Sep 29, 2017 at 9:00 AM, Jeff wrote:
> James,
>
> I had to do a hard reload of the page in
James,
I had to do a hard reload of the page in Chrome, since the browser kept
showing me a cached version without my key. After the hard reload, I can
see my key at https://dist.apache.org/repos/dist/dev/nifi/KEYS. Could you
try opening the KEYS link in incognito mode and verify that my key is
+1 (binding). I ran through the release helper including signature, hashes,
build, and testing the binary. I checked the LICENSE and NOTICE files.
Everything looks good to me.
One thing I noted is that Jeff's GPG key is not yet in the public KEYS file
at
87bcfb44e05b7bb96d0149f
> > >
> > > Have I done something wrong?
> > >
> > > -Mark
> > >
> > >
> > > -- Forwarded message --
> > > From: Jeff <jsto...@apache.org>
> > > Date: Thu, Sep 28, 2017 at 3:54 PM
>
og' is
> > feaf44b623be3201987bcfb44e05b7bb96d0149f
> >
> > Have I done something wrong?
> >
> > -Mark
> >
> >
> > -- Forwarded message --
> > From: Jeff <jsto...@apache.org>
> > Date: Thu, Sep 28, 2017 at 3:54 PM
ache.org>
> Date: Thu, Sep 28, 2017 at 3:54 PM
> Subject: [VOTE] Release Apache NiFi 1.4.0 (RC2)
> To: "dev@nifi.apache.org" <dev@nifi.apache.org>
>
>
> Hello,
>
> I am pleased to be calling this vote for the source release of Apache NiFi
> nifi-1.4.0.
>
[VOTE] Release Apache NiFi 1.4.0 (RC2)
To: "dev@nifi.apache.org" <dev@nifi.apache.org>
Hello,
I am pleased to be calling this vote for the source release of Apache NiFi
nifi-1.4.0.
The source zip, including signatures, digests, etc. can be found at:
https://repository.apache.or
+1 non-binding.
All processor, controller service, and reporting tasks look good.
Rick.
--
Richard St. John, PhD
Asymmetrik
141 National Business Pkwy, Suite 110
Annapolis Junction, MD 20701
On Sep 28, 2017, 3:54 PM -0400, Jeff , wrote:
> Hello,
>
> I am pleased to be
Hello,
I am pleased to be calling this vote for the source release of Apache NiFi
nifi-1.4.0.
The source zip, including signatures, digests, etc. can be found at:
https://repository.apache.org/content/repositories/orgapachenifi-
The Git tag is nifi-1.4.0-RC2
The Git commit ID is
Hello all,
I just wanted to send out a quick update on RC2 status. I'm currently
running the "mvn release:perform" step, which should be nearing
completion. There are a few steps to do once that has finished, but there
should be a new voting thread very soon.
I want to thank all of you for
Yes, currently working on RC2.
On Thu, Sep 28, 2017 at 12:30 PM Brandon DeVries wrote:
> Jeff,
>
> Any updates on RC2?
>
> Brandon
>
> On Mon, Sep 25, 2017 at 4:56 PM Jeff wrote:
>
> > Mark,
> >
> > I also would like to get RC2 out as soon as possible, but due
Jeff,
Any updates on RC2?
Brandon
On Mon, Sep 25, 2017 at 4:56 PM Jeff wrote:
> Mark,
>
> I also would like to get RC2 out as soon as possible, but due to time
> constraints on other tasks, I will not be able to create RC2 until tomorrow
> afternoon. However, with a
Mark,
I also would like to get RC2 out as soon as possible, but due to time
constraints on other tasks, I will not be able to create RC2 until tomorrow
afternoon. However, with a 72-hour voting window resulting in binding
votes to release RC2, 1.4.0 could be released by the end of the week.
Jeff,
All outstanding issues have been resolved/committed, right? Can RC2 get
turned around quickly? We were hoping to have an official 1.4.0 release by
the end of the week.
Thanks,
Mark
On Mon, Sep 25, 2017 at 2:51 PM, Jeff wrote:
> Given the issues discovered today, I
Given the issues discovered today, I am canceling the voting for RC1.
I will prepare RC2 when I get a bit of time to work on it, hopefully within
the next day or two, and start another vote thread.
Here's a list of issues that will be addressed by RC2:
Ok good this makes a lot more sense now. One JIRA will fix the
erroneous duplicates. And this JIRA, which can be done later, will
correct that we should have actually not even have noticed the
duplicates and Rick's flow should have worked correctly automatically
[1].
[1]
I think the reason for the upgrade issue was the following...
Normally there is an automatic upgrade of component versions, with the
following logic:
- If the flow says you are using version X of a component, and during
startup version X is not found, but version Y is found, and version Y
is the
All,
I verified that Joey is correct and that dependency causes the
duplicates. I reopened NIFI-4345 and submitted a PR.
Regards,
Matt
[1] https://issues.apache.org/jira/browse/NIFI-4345
[2] https://github.com/apache/nifi/pull/2174
On Mon, Sep 25, 2017 at 11:45 AM, Richard St. John
Joey,
That sounds like that is the issue.
Rick.
--
Richard St. John, PhD
Asymmetrik
141 National Business Pkwy, Suite 110
Annapolis Junction, MD 20701
On Sep 25, 2017, 11:44 AM -0400, Joey Frazee , wrote:
> I think there could be an issue with the deps in the
>
I think there could be an issue with the deps in the nifi-mongodb-services-nar.
It includes nifi-lookup-services which should either be unnecessary or should
just be provided scope (just need the services API dependency). So it’s
possible that all the impls in nifi-lookup-services are indeed
Joe,
The issue I encountered was related to, I believe, the packaging of the mongodb
lookup service. I am using the XMLlookup service and have a processor with a
reference to the XML lookup service. When I upgraded from 1.3 to 1.4, the
processor became invalid due to “incompatible type” of
-1 (binding) based on what Rick ran into.
Otherwise though the release is looking good. I'm running through a
series of tests now and things going well.
Rick,
I agree there are duplicate controller services and sourced to the
mongo system. And we must fix/remove those.
However, the issue for
-1 non-binding.
There are duplicate lookup services registered and it’s causing issues
upgrading from 1.3.0 to 1.4.0. It seems to be related to the mongo lookup
service.
Rick.
--
Richard St. John, PhD
Asymmetrik
141 National Business Pkwy, Suite 110
Annapolis Junction, MD 20701
On Sep 24,
Hello,
I am pleased to be calling this vote for the source release of Apache NiFi
nifi-1.4.0.
The source zip, including signatures, digests, etc. can be found at:
https://repository.apache.org/content/repositories/orgapachenifi-1110
The Git tag is nifi-1.4.0-RC1
The Git commit ID is
44 matches
Mail list logo