You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@nifi.apache.org by Joe Witt <jo...@gmail.com> on 2021/02/01 17:14:34 UTC
Re: [DISCUSS] Release of Apache NiFi 1.13.0
Team,
Will put RC2 for 1.13 back up today hopefully. The fix is in for the issue
that sank the release.
Thanks
Joe
On Thu, Jan 28, 2021 at 8:18 AM Joe Witt <jo...@gmail.com> wrote:
> Otto
>
> Truth is we dont know. We cannot readily test with the amazing matrix
> that exists. So we are leaning toward ensuring recent versions work as
> expected.
>
> The goal is java 8 and 11 broadly right now. But these internal changes of
> exception types being used are brutal.
>
> Thanks
>
> On Thu, Jan 28, 2021 at 8:15 AM Otto Fowler <ot...@gmail.com>
> wrote:
>
>> Thanks Joe,
>>
>> I’m started down that road right after I sent this. I’ll update when I
>> know.
>> I _have_ been building nifi with this jdk all along though.
>>
>> If there are jdk minimum requirements, should they be documented ( or are
>> they and I missed it)?
>>
>> > On Jan 28, 2021, at 09:35, Joe Witt <jo...@gmail.com> wrote:
>> >
>> > Otto
>> >
>> > I dont know we can keep all variants of Java 8 happy. That one is
>> nearly
>> > three years old. I would say try with something more recent. It has
>> been
>> > pretty shocking how many api changes we have seen across these builds.
>> >
>> > Thanks
>> >
>> > On Thu, Jan 28, 2021 at 6:12 AM Otto Fowler <ot...@gmail.com>
>> wrote:
>> >
>> >> I’m trying to validate RC-1 and I’m seeing this exception building /
>> >> running tests
>> >>
>> >> [INFO] Running org.apache.nifi.processors.standard.TestListenTCP
>> >> [ERROR] Tests run: 6, Failures: 1, Errors: 0, Skipped: 0, Time elapsed:
>> >> 4.499 s <<< FAILURE! - in
>> org.apache.nifi.processors.standard.TestListenTCP
>> >> [ERROR]
>> >>
>> testTLSClientAuthRequiredAndClientCertNotProvided(org.apache.nifi.processors.standard.TestListenTCP)
>> >> Time elapsed: 0.127 s <<< FAILURE!
>> >> java.lang.AssertionError: unexpected exception type thrown;
>> >> expected:<javax.net.ssl.SSLException> but
>> was:<java.net.SocketException>
>> >> at
>> >>
>> org.apache.nifi.processors.standard.TestListenTCP.testTLSClientAuthRequiredAndClientCertNotProvided(TestListenTCP.java:159)
>> >> Caused by: java.net.SocketException: Connection reset
>> >> at
>> >>
>> org.apache.nifi.processors.standard.TestListenTCP.runTCP(TestListenTCP.java:209)
>> >> at
>> >>
>> org.apache.nifi.processors.standard.TestListenTCP.lambda$testTLSClientAuthRequiredAndClientCertNotProvided$0(TestListenTCP.java:160)
>> >> at
>> >>
>> org.apache.nifi.processors.standard.TestListenTCP.testTLSClientAuthRequiredAndClientCertNotProvided(TestListenTCP.java:159)
>> >>
>> >>
>> >>
>> >> Apache Maven 3.6.3 (cecedd343002696d0abb50b32b541b8a6ba2883f)
>> >> Maven home: /usr/local/Cellar/maven/3.6.3_1/libexec
>> >> Java version: 1.8.0_171, vendor: Oracle Corporation, runtime:
>> >> /Library/Java/JavaVirtualMachines/jdk1.8.0_171.jdk/Contents/Home/jre
>> >> Default locale: en_US, platform encoding: UTF-8
>> >> OS name: "mac os x", version: "10.16", arch: "x86_64", family: “mac"
>> >>
>> >>
>> >>
>> >>> On Jan 27, 2021, at 10:31, Joe Witt <jo...@gmail.com> wrote:
>> >>>
>> >>> ...in this brutal game of wach a mole another couple brittle tests
>> have
>> >>> emerged on the Java 11 line.
>> >>> https://issues.apache.org/jira/browse/NIFI-8177 will get that looked
>> >> into.
>> >>> And I'm also seeing if for some reason adding a bit more
>> horsepower/cpu
>> >>> usage to the github tests will help. Things had been very stable for
>> >> quite
>> >>> a while until the update to the latest 11.0.10 azul jdk came out so
>> kind
>> >> of
>> >>> strange the tests became less reliable then. Anyway dont want to
>> initiate
>> >>> the RC until things seem stable otherwise it makes the vote process
>> more
>> >>> difficult and further when the builds dont pass it makes the already
>> >>> difficult task of staying apace with PRs more inivolved.
>> >>>
>> >>> Thanks
>> >>>
>> >>> On Wed, Jan 27, 2021 at 12:19 AM Pierre Villard <
>> >> pierre.villard.fr@gmail.com>
>> >>> wrote:
>> >>>
>> >>>> Awesome, thanks Joe!
>> >>>>
>> >>>> Le mer. 27 janv. 2021 à 10:16, Joe Witt <jo...@gmail.com> a
>> écrit :
>> >>>>
>> >>>>> Team,
>> >>>>>
>> >>>>> Ok wow so the issue with build failures that emerged has been
>> resolved
>> >> it
>> >>>>> appears thanks to a lot of effort by exceptionfactory. The other
>> >>>> lingering
>> >>>>> commits/PRs are in and I think most of what folks asked for in this
>> >>>>> thread. I just put in a commit which drops a few older/less common
>> >> nars
>> >>>>> from convenience binary inclusion to get us back under the maximum
>> size
>> >>>>> again. And now I think we can initiate RC1 build for 1.13.0.
>> >>>>>
>> >>>>> That should be published in the AM.
>> >>>>>
>> >>>>> Thanks
>> >>>>>
>> >>>>> On Mon, Jan 25, 2021 at 6:40 AM Joe Witt <jo...@gmail.com>
>> wrote:
>> >>>>>
>> >>>>>> Team,
>> >>>>>>
>> >>>>>> There is a TZ handling issue
>> >>>>>> https://issues.apache.org/jira/browse/NIFI-8023 that needs a
>> >>>> resolution
>> >>>>>> and there is also a new issue that has emerged on Github Actions/CI
>> >>>>>> https://github.com/apache/nifi/actions which is resulting in
>> broken
>> >>>>>> builds. This emerged in the latest Java 11 Azul release and in
>> Github
>> >>>>> CI.
>> >>>>>> I've tried to replicate with no success on a local linux machine
>> with
>> >>>> the
>> >>>>>> exact same JVM/version.
>> >>>>>>
>> >>>>>> Once these are wrapped I'll initiate the RC. Great work to all
>> >>>> involved
>> >>>>>> in helping get the release candidate this close.
>> >>>>>>
>> >>>>>> Thanks
>> >>>>>> Joe
>> >>>>>>
>> >>>>>> On Thu, Jan 21, 2021 at 8:30 AM Joe Witt <jo...@gmail.com>
>> wrote:
>> >>>>>>
>> >>>>>>> Team,
>> >>>>>>>
>> >>>>>>> A couple 1.13 tagged items still lingering. Going to either kick
>> >> them
>> >>>>>>> out or merge them and get going. Hopefully an RC today or
>> tomorrow.
>> >>>>>>>
>> >>>>>>> Thanks
>> >>>>>>>
>> >>>>>>> On Wed, Jan 20, 2021 at 7:21 AM Mike Thomsen <
>> mikerthomsen@gmail.com
>> >>>
>> >>>>>>> wrote:
>> >>>>>>>
>> >>>>>>>> Bug confirmed. Working on a PR now.
>> >>>>>>>>
>> >>>>>>>> On Wed, Jan 20, 2021 at 8:45 AM Mike Thomsen <
>> >> mikerthomsen@gmail.com
>> >>>>>
>> >>>>>>>> wrote:
>> >>>>>>>>>
>> >>>>>>>>> This morning, I think I found a serious bug in
>> PutCassandraRecord
>> >>>> WRT
>> >>>>>>>>> writing binary data to Cassandra. I'm debugging now. If it's
>> >>>> really a
>> >>>>>>>>> bug, I'd appreciate it if we could squeak a fix into 1.13.
>> >>>>>>>>>
>> >>>>>>>>> On Tue, Jan 19, 2021 at 9:54 AM Joe Witt <jo...@gmail.com>
>> >>>> wrote:
>> >>>>>>>>>>
>> >>>>>>>>>> Team,
>> >>>>>>>>>>
>> >>>>>>>>>> I'm going to initiate RM processes for 1.13. I'll be watching
>> >>>>>>>> closely for
>> >>>>>>>>>> currently tagged 1.13 items to include. If anything is
>> dragging
>> >>>>>>>> I'll just
>> >>>>>>>>>> remove it from 1.13 and we'll pick it up later. Other items
>> that
>> >>>>> get
>> >>>>>>>>>> dev/reviewer traction before I cut the RC we can include. I
>> will
>> >>>>>>>>>> *probably/hopefully* start that process first thing tomorrow
>> >>>>> morning.
>> >>>>>>>>>>
>> >>>>>>>>>> https://issues.apache.org/jira/projects/NIFI/versions/12348700
>> >>>> is
>> >>>>>>>> what i'm
>> >>>>>>>>>> working from.
>> >>>>>>>>>>
>> >>>>>>>>>> Thanks
>> >>>>>>>>>>
>> >>>>>>>>>> On Fri, Jan 15, 2021 at 6:12 PM Waleed Aibany <
>> >>>> walmut44@gmail.com>
>> >>>>>>>> wrote:
>> >>>>>>>>>>
>> >>>>>>>>>>> Hi,
>> >>>>>>>>>>>
>> >>>>>>>>>>> I did rebase to this old PR
>> >>>>>>>> https://github.com/apache/nifi/pull/4167
>> >>>>>>>>>>> Is it possible to include it in 1.13.0
>> >>>>>>>>>>>
>> >>>>>>>>>>> Thank you
>> >>>>>>>>>>>
>> >>>>>>>>>>> On 2021/01/05 15:03:32, Pierre Villard <
>> >>>>>>>> pierre.villard.fr@gmail.com>
>> >>>>>>>>>>> wrote:
>> >>>>>>>>>>>> Hi all,
>> >>>>>>>>>>>>
>> >>>>>>>>>>>> Happy new year to everyone, hope you all had a great time.
>> >>>> I'm
>> >>>>>>>> bumping
>> >>>>>>>>>>> this
>> >>>>>>>>>>>> thread up as I think it'd make a lot of sense to release NiFi
>> >>>>>>>> 1.13.0. We
>> >>>>>>>>>>>> have a ton of bug fixes and improvements that would be very
>> >>>>>>>> useful for
>> >>>>>>>>>>> our
>> >>>>>>>>>>>> community.
>> >>>>>>>>>>>>
>> >>>>>>>>>>>> Let's try to see if there are any blockers for a release and
>> >>>>>>>> start the
>> >>>>>>>>>>>> process:
>> >>>>>>>>>>>>
>> >>>>>>>>>>>
>> >>>>>>>>
>> >>>>>
>> >>>>
>> >>
>> https://issues.apache.org/jira/issues/?jql=project%20%3D%20NIFI%20AND%20resolution%20%3D%20Unresolved%20AND%20fixVersion%20%3D%201.13.0%20ORDER%20BY%20priority%20DESC%2C%20updated%20DESC
>> >>>>>>>>>>>>
>> >>>>>>>>>>>> Thanks!
>> >>>>>>>>>>>>
>> >>>>>>>>>>>>
>> >>>>>>>>>>>> Le mar. 1 déc. 2020 à 14:49, Bryan Bende <bb...@gmail.com>
>> >>>> a
>> >>>>>>>> écrit :
>> >>>>>>>>>>>>
>> >>>>>>>>>>>>> Chris,
>> >>>>>>>>>>>>>
>> >>>>>>>>>>>>> The illegal reflective access warnings are expected when
>> >>>>>>>> running on
>> >>>>>>>>>>> Java
>> >>>>>>>>>>>>> 11.
>> >>>>>>>>>>>>>
>> >>>>>>>>>>>>> The second warning about the provenance repo seems like a
>> >>>>>>>> possible
>> >>>>>>>>>>>>> issue due to some recent refactorings made for stateless,
>> >>>> we
>> >>>>>>>> should
>> >>>>>>>>>>>>> take a look at that.
>> >>>>>>>>>>>>>
>> >>>>>>>>>>>>> Thanks,
>> >>>>>>>>>>>>>
>> >>>>>>>>>>>>> Bryan
>> >>>>>>>>>>>>>
>> >>>>>>>>>>>>> On Tue, Dec 1, 2020 at 3:58 AM Chris Sampson
>> >>>>>>>>>>>>> <ch...@naimuri.com.invalid> wrote:
>> >>>>>>>>>>>>>>
>> >>>>>>>>>>>>>> Just spotted the following during startup of NiFi
>> >>>>>>>> 1.13.0-SNAPSHOT on
>> >>>>>>>>>>> my
>> >>>>>>>>>>>>>> local machine, which might be worth looking at (although
>> >>>>>>>> I've not
>> >>>>>>>>>>> deleted
>> >>>>>>>>>>>>>> and re-created the binaries in a little while, so I could
>> >>>>>>>> have
>> >>>>>>>>>>> something
>> >>>>>>>>>>>>>> wrong in my /lib folder or such):
>> >>>>>>>>>>>>>>
>> >>>>>>>>>>>>>> 2020-12-01 08:52:48,382 ERROR [NiFi logging handler]
>> >>>>>>>>>>>>> org.apache.nifi.StdErr
>> >>>>>>>>>>>>>> WARNING: An illegal reflective access operation has
>> >>>>> occurred
>> >>>>>>>>>>>>>> 2020-12-01 08:52:48,383 ERROR [NiFi logging handler]
>> >>>>>>>>>>>>> org.apache.nifi.StdErr
>> >>>>>>>>>>>>>> WARNING: Illegal reflective access by
>> >>>>>>>>>>>>>> com.sun.xml.bind.v2.runtime.reflect.opt.Injector
>> >>>>>>>>>>>>>>
>> >>>>>>>> (file:.../nifi-1.13.0-SNAPSHOT/lib/java11/jaxb-impl-2.3.0.jar) to
>> >>>>>>>>>>> method
>> >>>>>>>>>>>>>>
>> >>>>>>>>
>> java.lang.ClassLoader.defineClass(java.lang.String,byte[],int,int)
>> >>>>>>>>>>>>>> 2020-12-01 08:52:48,383 ERROR [NiFi logging handler]
>> >>>>>>>>>>>>> org.apache.nifi.StdErr
>> >>>>>>>>>>>>>> WARNING: Please consider reporting this to the
>> >>>> maintainers
>> >>>>> of
>> >>>>>>>>>>>>>> com.sun.xml.bind.v2.runtime.reflect.opt.Injector
>> >>>>>>>>>>>>>> 2020-12-01 08:52:48,383 ERROR [NiFi logging handler]
>> >>>>>>>>>>>>> org.apache.nifi.StdErr
>> >>>>>>>>>>>>>> WARNING: Use --illegal-access=warn to enable warnings of
>> >>>>>>>> further
>> >>>>>>>>>>> illegal
>> >>>>>>>>>>>>>> reflective access operations
>> >>>>>>>>>>>>>> 2020-12-01 08:52:48,383 ERROR [NiFi logging handler]
>> >>>>>>>>>>>>> org.apache.nifi.StdErr
>> >>>>>>>>>>>>>> WARNING: All illegal access operations will be denied in
>> >>>> a
>> >>>>>>>> future
>> >>>>>>>>>>> release
>> >>>>>>>>>>>>>>
>> >>>>>>>>>>>>>> Also:
>> >>>>>>>>>>>>>> 2020-12-01 08:52:52,486 WARN [main]
>> >>>>>>>>>>>>>> o.a.n.n.StandardExtensionDiscoveringManager Failed to
>> >>>>>>>> register
>> >>>>>>>>>>> extension
>> >>>>>>>>>>>>>> org.apache.nifi.provenance.VolatileProvenanceRepository
>> >>>> due
>> >>>>>>>> to:
>> >>>>>>>>>>> Attempt
>> >>>>>>>>>>>>> was
>> >>>>>>>>>>>>>> made to load
>> >>>>>>>> org.apache.nifi.provenance.VolatileProvenanceRepository
>> >>>>>>>>>>> from
>> >>>>>>>>>>>>>>
>> >>>>>>>> org.apache.nifi:nifi-provenance-repository-nar:1.13.0-SNAPSHOT
>> but
>> >>>>>>>>>>> that
>> >>>>>>>>>>>>>> class name is already loaded/registered from
>> >>>>>>>>>>>>>> org.apache.nifi:nifi-stateless-nar:1.13.0-SNAPSHOT and
>> >>>>>>>> multiple
>> >>>>>>>>>>> versions
>> >>>>>>>>>>>>>> are not supported for this type
>> >>>>>>>>>>>>>>
>> >>>>>>>>>>>>>> These log messages appear just before the NAR extraction
>> >>>>>>>> logs during
>> >>>>>>>>>>>>>> instance startup.
>> >>>>>>>>>>>>>>
>> >>>>>>>>>>>>>> Don't know whether these are things that should be fixed
>> >>>>>>>> before
>> >>>>>>>>>>> 1.13.0
>> >>>>>>>>>>>>>> and/or have already been looked into, but figured I'd
>> >>>>>>>> mention them so
>> >>>>>>>>>>>>>> they're at least known about.
>> >>>>>>>>>>>>>>
>> >>>>>>>>>>>>>> ---
>> >>>>>>>>>>>>>> *Chris Sampson*
>> >>>>>>>>>>>>>> IT Consultant
>> >>>>>>>>>>>>>> chris.sampson@naimuri.com
>> >>>>>>>>>>>>>> <https://www.naimuri.com/>
>> >>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>
>> >>>>>>>>>>>>>> On Mon, 30 Nov 2020 at 18:50, Nissim Shiman
>> >>>>>>>>>>> <ns...@yahoo.com.invalid>
>> >>>>>>>>>>>>>> wrote:
>> >>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>> Hello Nifi Team,
>> >>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>> NIFI-7738 [1]
>> >>>> https://github.com/apache/nifi/pull/4563
>> >>>>>>>>>>>>>>> has already been reviewed/tested by a fellow
>> >>>> contributer
>> >>>>>>>>>>>>>>> I would greatly appreciate a committer moving this to
>> >>>>> main
>> >>>>>>>> for
>> >>>>>>>>>>> 1.13.0
>> >>>>>>>>>>>>>>> Thanks,
>> >>>>>>>>>>>>>>> Nissim Shiman
>> >>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>> [1] https://issues.apache.org/jira/browse/NIFI-7738
>> >>>>>>>>>>>>>>> On Sunday, November 29, 2020, 07:12:12 PM EST, Matt
>> >>>>>>>> Burgess <
>> >>>>>>>>>>>>>>> mattyb149@apache.org> wrote:
>> >>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>> I just merged Mike's Cassandra DMC PR, reviewing the
>> >>>>>>>> graph stuff
>> >>>>>>>>>>> now.
>> >>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>> I have a bunch of open PRs [1], I don't think any are
>> >>>>>>>> blockers for
>> >>>>>>>>>>>>>>> 1.13.0 but thought I'd take this opportunity to find
>> >>>> some
>> >>>>>>>>>>> reviewers :)
>> >>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>> Regards,
>> >>>>>>>>>>>>>>> Matt
>> >>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>> [1] https://github.com/apache/nifi/pulls/mattyb149
>> >>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>> On Sat, Nov 28, 2020 at 10:13 AM Phillip Grenier
>> >>>>>>>>>>> <ph...@nifi.rocks>
>> >>>>>>>>>>>>>>> wrote:
>> >>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>> I wouldn't mind
>> >>>>> https://github.com/apache/nifi/pull/4554
>> >>>>>>>> making
>> >>>>>>>>>>> it
>> >>>>>>>>>>>>> in.
>> >>>>>>>>>>>>>>> Have
>> >>>>>>>>>>>>>>>> seen a couple more instances where people have
>> >>>> created
>> >>>>>>>> custom
>> >>>>>>>>>>>>> processors
>> >>>>>>>>>>>>>>> to
>> >>>>>>>>>>>>>>>> work around this PR.
>> >>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>> On Thu, Nov 26, 2020 at 11:10 AM Mike Thomsen <
>> >>>>>>>>>>>>> mikerthomsen@gmail.com>
>> >>>>>>>>>>>>>>>> wrote:
>> >>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>>> Also, for most of us (committers and community
>> >>>>>>>> members), it's a
>> >>>>>>>>>>>>>>>>> holiday season so might be good to delay a release
>> >>>> to
>> >>>>>>>> early
>> >>>>>>>>>>> January
>> >>>>>>>>>>>>>>>>> anyway. Just a thought.
>> >>>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>>> On Thu, Nov 26, 2020 at 11:08 AM Mike Thomsen <
>> >>>>>>>>>>>>> mikerthomsen@gmail.com>
>> >>>>>>>>>>>>>>>>> wrote:
>> >>>>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>>>> https://github.com/apache/nifi/pull/4638 - This
>> >>>> is
>> >>>>>>>> a big
>> >>>>>>>>>>>>> increase in
>> >>>>>>>>>>>>>>>>>> graph functionality, and I want to give him a
>> >>>>> chance
>> >>>>>>>> to get
>> >>>>>>>>>>> his
>> >>>>>>>>>>>>> first
>> >>>>>>>>>>>>>>>>>> contribution in with 1.13 (we may have some more
>> >>>> of
>> >>>>>>>> his work
>> >>>>>>>>>>> we
>> >>>>>>>>>>>>> can
>> >>>>>>>>>>>>>>>>>> open source).
>> >>>>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>>>> Matt's also reviewing some of my Cassandra and
>> >>>>> graph
>> >>>>>>>> tickets
>> >>>>>>>>>>> as
>> >>>>>>>>>>>>> well.
>> >>>>>>>>>>>>>>>>>> I wouldn't call those **blockers**, but having
>> >>>> the
>> >>>>>>>> Cassandra
>> >>>>>>>>>>> DMC
>> >>>>>>>>>>>>>>> fully
>> >>>>>>>>>>>>>>>>>> fleshed out would be nice.
>> >>>>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>>>> On Thu, Nov 26, 2020 at 9:10 AM Otto Fowler <
>> >>>>>>>>>>>>> ottobackwards@gmail.com
>> >>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>>> wrote:
>> >>>>>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>>>>> NIFI-7795
>> >>>>>>>> https://github.com/apache/nifi/pull/4656
>> >>>>>>>>>>>>>>>>>>> NIFI-7761
>> >>>>> https://github.com/apache/nifi/pull/4513
>> >>>>>>>>>>>>>>>>>>> NIFI-2072
>> >>>>> https://github.com/apache/nifi/pull/4384
>> >>>>>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>>>>> From: Pierre Villard <
>> >>>>> pierre.villard.fr@gmail.com>
>> >>>>>>>>>>>>>>>>>>> <pi...@gmail.com>
>> >>>>>>>>>>>>>>>>>>> Reply: dev@nifi.apache.org <
>> >>>> dev@nifi.apache.org>
>> >>>>> <
>> >>>>>>>>>>>>>>> dev@nifi.apache.org>
>> >>>>>>>>>>>>>>>>>>> Date: November 26, 2020 at 04:55:56
>> >>>>>>>>>>>>>>>>>>> To: dev@nifi.apache.org <de...@nifi.apache.org>
>> >>>> <
>> >>>>>>>>>>>>> dev@nifi.apache.org
>> >>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>>>>> Subject: [DISCUSS] Release of Apache NiFi
>> >>>> 1.13.0
>> >>>>>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>>>>> Hi community,
>> >>>>>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>>>>> Starting a discussion thread around the release
>> >>>>> of
>> >>>>>>>> NiFi
>> >>>>>>>>>>>>> 1.13.0. We
>> >>>>>>>>>>>>>>>>> added
>> >>>>>>>>>>>>>>>>>>> quite a lot of significant improvements and
>> >>>>>>>> features since
>> >>>>>>>>>>> the
>> >>>>>>>>>>>>>>> release
>> >>>>>>>>>>>>>>>>> of
>> >>>>>>>>>>>>>>>>>>> 1.12.1 - I see 143 JIRAs with 1.13.0 as the fix
>> >>>>>>>> version. I
>> >>>>>>>>>>>>> think it
>> >>>>>>>>>>>>>>>>> makes
>> >>>>>>>>>>>>>>>>>>> sense to consider a new release.
>> >>>>>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>>>>> Please share here the JIRAs with opened pull
>> >>>>>>>> requests that
>> >>>>>>>>>>> we
>> >>>>>>>>>>>>> would
>> >>>>>>>>>>>>>>>>> need to
>> >>>>>>>>>>>>>>>>>>> look at to make this release happen.
>> >>>>>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>>>>> Thanks,
>> >>>>>>>>>>>>>>>>>>> Pierre
>> >>>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>
>> >>>>>>>>>>>>
>> >>>>>>>>>>>
>> >>>>>>>>
>> >>>>>>>
>> >>>>>
>> >>>>
>> >>
>> >>
>>
>>
Re: [DISCUSS] Release of Apache NiFi 1.13.0
Posted by Joe Witt <jo...@gmail.com>.
Yep fixed the glitch so to speak. We do have the others doc'd and those
I'm familiar with keeping them at the release version. These I didn't know
about. But I think we're good now anyway.
Thanks
On Mon, Feb 1, 2021 at 4:50 PM Joey Frazee <jo...@icloud.com.invalid>
wrote:
> You’ve fixed it now by removing it, but I took a look at the history and
> that module just wasn’t a dependency of anything anymore and the release
> plugin doesn’t automatically update the version in that case.
>
> I think the RM guidance might just be “check that <version /> was
> correctly updated” to catch this when it might matter.
>
> -joey
>
> > On Feb 1, 2021, at 1:33 PM, Joe Witt <jo...@gmail.com> wrote:
> >
> > Team
> >
> > starting RC2. Joey Frazee noted "I noticed that
> > nifi-docker/dockermaven-stateless/pom.xml
> > and nifi-docker/docker-compose/docker-compose.yml in the source package
> and
> > tag are still using 1.13.0-SNAPSHOT" while looking at RC1. I have no
> > instructions/guidance on what to do with those as an RM and I've never
> > modified them before. If we're going to keep these in the build, and I
> > would advocate actually that we remove them, then someone needs to
> > determine the whole lifecycle of how to manage/maintain them and
> > document the steps for a RelMgr. The dockerhub module we do have
> guidance
> > for and they're currently correct.
> >
> > Thanks
> >
> >> On Mon, Feb 1, 2021 at 10:14 AM Joe Witt <jo...@gmail.com> wrote:
> >>
> >> Team,
> >>
> >> Will put RC2 for 1.13 back up today hopefully. The fix is in for the
> >> issue that sank the release.
> >>
> >> Thanks
> >> Joe
> >>
> >>> On Thu, Jan 28, 2021 at 8:18 AM Joe Witt <jo...@gmail.com> wrote:
> >>>
> >>> Otto
> >>>
> >>> Truth is we dont know. We cannot readily test with the amazing matrix
> >>> that exists. So we are leaning toward ensuring recent versions work as
> >>> expected.
> >>>
> >>> The goal is java 8 and 11 broadly right now. But these internal changes
> >>> of exception types being used are brutal.
> >>>
> >>> Thanks
> >>>
> >>> On Thu, Jan 28, 2021 at 8:15 AM Otto Fowler <ot...@gmail.com>
> >>> wrote:
> >>>
> >>>> Thanks Joe,
> >>>>
> >>>> I’m started down that road right after I sent this. I’ll update when
> I
> >>>> know.
> >>>> I _have_ been building nifi with this jdk all along though.
> >>>>
> >>>> If there are jdk minimum requirements, should they be documented ( or
> >>>> are they and I missed it)?
> >>>>
> >>>>> On Jan 28, 2021, at 09:35, Joe Witt <jo...@gmail.com> wrote:
> >>>>>
> >>>>> Otto
> >>>>>
> >>>>> I dont know we can keep all variants of Java 8 happy. That one is
> >>>> nearly
> >>>>> three years old. I would say try with something more recent. It has
> >>>> been
> >>>>> pretty shocking how many api changes we have seen across these
> builds.
> >>>>>
> >>>>> Thanks
> >>>>>
> >>>>> On Thu, Jan 28, 2021 at 6:12 AM Otto Fowler <ottobackwards@gmail.com
> >
> >>>> wrote:
> >>>>>
> >>>>>> I’m trying to validate RC-1 and I’m seeing this exception building /
> >>>>>> running tests
> >>>>>>
> >>>>>> [INFO] Running org.apache.nifi.processors.standard.TestListenTCP
> >>>>>> [ERROR] Tests run: 6, Failures: 1, Errors: 0, Skipped: 0, Time
> >>>> elapsed:
> >>>>>> 4.499 s <<< FAILURE! - in
> >>>> org.apache.nifi.processors.standard.TestListenTCP
> >>>>>> [ERROR]
> >>>>>>
> >>>>
> testTLSClientAuthRequiredAndClientCertNotProvided(org.apache.nifi.processors.standard.TestListenTCP)
> >>>>>> Time elapsed: 0.127 s <<< FAILURE!
> >>>>>> java.lang.AssertionError: unexpected exception type thrown;
> >>>>>> expected:<javax.net.ssl.SSLException> but
> >>>> was:<java.net.SocketException>
> >>>>>> at
> >>>>>>
> >>>>
> org.apache.nifi.processors.standard.TestListenTCP.testTLSClientAuthRequiredAndClientCertNotProvided(TestListenTCP.java:159)
> >>>>>> Caused by: java.net.SocketException: Connection reset
> >>>>>> at
> >>>>>>
> >>>>
> org.apache.nifi.processors.standard.TestListenTCP.runTCP(TestListenTCP.java:209)
> >>>>>> at
> >>>>>>
> >>>>
> org.apache.nifi.processors.standard.TestListenTCP.lambda$testTLSClientAuthRequiredAndClientCertNotProvided$0(TestListenTCP.java:160)
> >>>>>> at
> >>>>>>
> >>>>
> org.apache.nifi.processors.standard.TestListenTCP.testTLSClientAuthRequiredAndClientCertNotProvided(TestListenTCP.java:159)
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>> Apache Maven 3.6.3 (cecedd343002696d0abb50b32b541b8a6ba2883f)
> >>>>>> Maven home: /usr/local/Cellar/maven/3.6.3_1/libexec
> >>>>>> Java version: 1.8.0_171, vendor: Oracle Corporation, runtime:
> >>>>>> /Library/Java/JavaVirtualMachines/jdk1.8.0_171.jdk/Contents/Home/jre
> >>>>>> Default locale: en_US, platform encoding: UTF-8
> >>>>>> OS name: "mac os x", version: "10.16", arch: "x86_64", family: “mac"
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>> On Jan 27, 2021, at 10:31, Joe Witt <jo...@gmail.com> wrote:
> >>>>>>>
> >>>>>>> ...in this brutal game of wach a mole another couple brittle tests
> >>>> have
> >>>>>>> emerged on the Java 11 line.
> >>>>>>> https://issues.apache.org/jira/browse/NIFI-8177 will get that
> looked
> >>>>>> into.
> >>>>>>> And I'm also seeing if for some reason adding a bit more
> >>>> horsepower/cpu
> >>>>>>> usage to the github tests will help. Things had been very stable
> for
> >>>>>> quite
> >>>>>>> a while until the update to the latest 11.0.10 azul jdk came out so
> >>>> kind
> >>>>>> of
> >>>>>>> strange the tests became less reliable then. Anyway dont want to
> >>>> initiate
> >>>>>>> the RC until things seem stable otherwise it makes the vote process
> >>>> more
> >>>>>>> difficult and further when the builds dont pass it makes the
> already
> >>>>>>> difficult task of staying apace with PRs more inivolved.
> >>>>>>>
> >>>>>>> Thanks
> >>>>>>>
> >>>>>>> On Wed, Jan 27, 2021 at 12:19 AM Pierre Villard <
> >>>>>> pierre.villard.fr@gmail.com>
> >>>>>>> wrote:
> >>>>>>>
> >>>>>>>> Awesome, thanks Joe!
> >>>>>>>>
> >>>>>>>> Le mer. 27 janv. 2021 à 10:16, Joe Witt <jo...@gmail.com> a
> >>>> écrit :
> >>>>>>>>
> >>>>>>>>> Team,
> >>>>>>>>>
> >>>>>>>>> Ok wow so the issue with build failures that emerged has been
> >>>> resolved
> >>>>>> it
> >>>>>>>>> appears thanks to a lot of effort by exceptionfactory. The other
> >>>>>>>> lingering
> >>>>>>>>> commits/PRs are in and I think most of what folks asked for in
> this
> >>>>>>>>> thread. I just put in a commit which drops a few older/less
> common
> >>>>>> nars
> >>>>>>>>> from convenience binary inclusion to get us back under the
> maximum
> >>>> size
> >>>>>>>>> again. And now I think we can initiate RC1 build for 1.13.0.
> >>>>>>>>>
> >>>>>>>>> That should be published in the AM.
> >>>>>>>>>
> >>>>>>>>> Thanks
> >>>>>>>>>
> >>>>>>>>> On Mon, Jan 25, 2021 at 6:40 AM Joe Witt <jo...@gmail.com>
> >>>> wrote:
> >>>>>>>>>
> >>>>>>>>>> Team,
> >>>>>>>>>>
> >>>>>>>>>> There is a TZ handling issue
> >>>>>>>>>> https://issues.apache.org/jira/browse/NIFI-8023 that needs a
> >>>>>>>> resolution
> >>>>>>>>>> and there is also a new issue that has emerged on Github
> >>>> Actions/CI
> >>>>>>>>>> https://github.com/apache/nifi/actions which is resulting in
> >>>> broken
> >>>>>>>>>> builds. This emerged in the latest Java 11 Azul release and in
> >>>> Github
> >>>>>>>>> CI.
> >>>>>>>>>> I've tried to replicate with no success on a local linux machine
> >>>> with
> >>>>>>>> the
> >>>>>>>>>> exact same JVM/version.
> >>>>>>>>>>
> >>>>>>>>>> Once these are wrapped I'll initiate the RC. Great work to all
> >>>>>>>> involved
> >>>>>>>>>> in helping get the release candidate this close.
> >>>>>>>>>>
> >>>>>>>>>> Thanks
> >>>>>>>>>> Joe
> >>>>>>>>>>
> >>>>>>>>>> On Thu, Jan 21, 2021 at 8:30 AM Joe Witt <jo...@gmail.com>
> >>>> wrote:
> >>>>>>>>>>
> >>>>>>>>>>> Team,
> >>>>>>>>>>>
> >>>>>>>>>>> A couple 1.13 tagged items still lingering. Going to either
> kick
> >>>>>> them
> >>>>>>>>>>> out or merge them and get going. Hopefully an RC today or
> >>>> tomorrow.
> >>>>>>>>>>>
> >>>>>>>>>>> Thanks
> >>>>>>>>>>>
> >>>>>>>>>>> On Wed, Jan 20, 2021 at 7:21 AM Mike Thomsen <
> >>>> mikerthomsen@gmail.com
> >>>>>>>
> >>>>>>>>>>> wrote:
> >>>>>>>>>>>
> >>>>>>>>>>>> Bug confirmed. Working on a PR now.
> >>>>>>>>>>>>
> >>>>>>>>>>>> On Wed, Jan 20, 2021 at 8:45 AM Mike Thomsen <
> >>>>>> mikerthomsen@gmail.com
> >>>>>>>>>
> >>>>>>>>>>>> wrote:
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> This morning, I think I found a serious bug in
> >>>> PutCassandraRecord
> >>>>>>>> WRT
> >>>>>>>>>>>>> writing binary data to Cassandra. I'm debugging now. If it's
> >>>>>>>> really a
> >>>>>>>>>>>>> bug, I'd appreciate it if we could squeak a fix into 1.13.
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> On Tue, Jan 19, 2021 at 9:54 AM Joe Witt <joe.witt@gmail.com
> >
> >>>>>>>> wrote:
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> Team,
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> I'm going to initiate RM processes for 1.13. I'll be
> watching
> >>>>>>>>>>>> closely for
> >>>>>>>>>>>>>> currently tagged 1.13 items to include. If anything is
> >>>> dragging
> >>>>>>>>>>>> I'll just
> >>>>>>>>>>>>>> remove it from 1.13 and we'll pick it up later. Other items
> >>>> that
> >>>>>>>>> get
> >>>>>>>>>>>>>> dev/reviewer traction before I cut the RC we can include. I
> >>>> will
> >>>>>>>>>>>>>> *probably/hopefully* start that process first thing tomorrow
> >>>>>>>>> morning.
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>>
> >>>> https://issues.apache.org/jira/projects/NIFI/versions/12348700
> >>>>>>>> is
> >>>>>>>>>>>> what i'm
> >>>>>>>>>>>>>> working from.
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> Thanks
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> On Fri, Jan 15, 2021 at 6:12 PM Waleed Aibany <
> >>>>>>>> walmut44@gmail.com>
> >>>>>>>>>>>> wrote:
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> Hi,
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> I did rebase to this old PR
> >>>>>>>>>>>> https://github.com/apache/nifi/pull/4167
> >>>>>>>>>>>>>>> Is it possible to include it in 1.13.0
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> Thank you
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> On 2021/01/05 15:03:32, Pierre Villard <
> >>>>>>>>>>>> pierre.villard.fr@gmail.com>
> >>>>>>>>>>>>>>> wrote:
> >>>>>>>>>>>>>>>> Hi all,
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> Happy new year to everyone, hope you all had a great time.
> >>>>>>>> I'm
> >>>>>>>>>>>> bumping
> >>>>>>>>>>>>>>> this
> >>>>>>>>>>>>>>>> thread up as I think it'd make a lot of sense to release
> >>>> NiFi
> >>>>>>>>>>>> 1.13.0. We
> >>>>>>>>>>>>>>>> have a ton of bug fixes and improvements that would be
> very
> >>>>>>>>>>>> useful for
> >>>>>>>>>>>>>>> our
> >>>>>>>>>>>>>>>> community.
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> Let's try to see if there are any blockers for a release
> and
> >>>>>>>>>>>> start the
> >>>>>>>>>>>>>>>> process:
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>
> >>>>>>>>
> >>>>>>
> >>>>
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20NIFI%20AND%20resolution%20%3D%20Unresolved%20AND%20fixVersion%20%3D%201.13.0%20ORDER%20BY%20priority%20DESC%2C%20updated%20DESC
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> Thanks!
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> Le mar. 1 déc. 2020 à 14:49, Bryan Bende <
> bbende@gmail.com>
> >>>>>>>> a
> >>>>>>>>>>>> écrit :
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>> Chris,
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>> The illegal reflective access warnings are expected when
> >>>>>>>>>>>> running on
> >>>>>>>>>>>>>>> Java
> >>>>>>>>>>>>>>>>> 11.
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>> The second warning about the provenance repo seems like a
> >>>>>>>>>>>> possible
> >>>>>>>>>>>>>>>>> issue due to some recent refactorings made for stateless,
> >>>>>>>> we
> >>>>>>>>>>>> should
> >>>>>>>>>>>>>>>>> take a look at that.
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>> Thanks,
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>> Bryan
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>> On Tue, Dec 1, 2020 at 3:58 AM Chris Sampson
> >>>>>>>>>>>>>>>>> <ch...@naimuri.com.invalid> wrote:
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>> Just spotted the following during startup of NiFi
> >>>>>>>>>>>> 1.13.0-SNAPSHOT on
> >>>>>>>>>>>>>>> my
> >>>>>>>>>>>>>>>>>> local machine, which might be worth looking at (although
> >>>>>>>>>>>> I've not
> >>>>>>>>>>>>>>> deleted
> >>>>>>>>>>>>>>>>>> and re-created the binaries in a little while, so I
> could
> >>>>>>>>>>>> have
> >>>>>>>>>>>>>>> something
> >>>>>>>>>>>>>>>>>> wrong in my /lib folder or such):
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>> 2020-12-01 08:52:48,382 ERROR [NiFi logging handler]
> >>>>>>>>>>>>>>>>> org.apache.nifi.StdErr
> >>>>>>>>>>>>>>>>>> WARNING: An illegal reflective access operation has
> >>>>>>>>> occurred
> >>>>>>>>>>>>>>>>>> 2020-12-01 08:52:48,383 ERROR [NiFi logging handler]
> >>>>>>>>>>>>>>>>> org.apache.nifi.StdErr
> >>>>>>>>>>>>>>>>>> WARNING: Illegal reflective access by
> >>>>>>>>>>>>>>>>>> com.sun.xml.bind.v2.runtime.reflect.opt.Injector
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>> (file:.../nifi-1.13.0-SNAPSHOT/lib/java11/jaxb-impl-2.3.0.jar)
> >>>> to
> >>>>>>>>>>>>>>> method
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>> java.lang.ClassLoader.defineClass(java.lang.String,byte[],int,int)
> >>>>>>>>>>>>>>>>>> 2020-12-01 08:52:48,383 ERROR [NiFi logging handler]
> >>>>>>>>>>>>>>>>> org.apache.nifi.StdErr
> >>>>>>>>>>>>>>>>>> WARNING: Please consider reporting this to the
> >>>>>>>> maintainers
> >>>>>>>>> of
> >>>>>>>>>>>>>>>>>> com.sun.xml.bind.v2.runtime.reflect.opt.Injector
> >>>>>>>>>>>>>>>>>> 2020-12-01 08:52:48,383 ERROR [NiFi logging handler]
> >>>>>>>>>>>>>>>>> org.apache.nifi.StdErr
> >>>>>>>>>>>>>>>>>> WARNING: Use --illegal-access=warn to enable warnings of
> >>>>>>>>>>>> further
> >>>>>>>>>>>>>>> illegal
> >>>>>>>>>>>>>>>>>> reflective access operations
> >>>>>>>>>>>>>>>>>> 2020-12-01 08:52:48,383 ERROR [NiFi logging handler]
> >>>>>>>>>>>>>>>>> org.apache.nifi.StdErr
> >>>>>>>>>>>>>>>>>> WARNING: All illegal access operations will be denied in
> >>>>>>>> a
> >>>>>>>>>>>> future
> >>>>>>>>>>>>>>> release
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>> Also:
> >>>>>>>>>>>>>>>>>> 2020-12-01 08:52:52,486 WARN [main]
> >>>>>>>>>>>>>>>>>> o.a.n.n.StandardExtensionDiscoveringManager Failed to
> >>>>>>>>>>>> register
> >>>>>>>>>>>>>>> extension
> >>>>>>>>>>>>>>>>>> org.apache.nifi.provenance.VolatileProvenanceRepository
> >>>>>>>> due
> >>>>>>>>>>>> to:
> >>>>>>>>>>>>>>> Attempt
> >>>>>>>>>>>>>>>>> was
> >>>>>>>>>>>>>>>>>> made to load
> >>>>>>>>>>>> org.apache.nifi.provenance.VolatileProvenanceRepository
> >>>>>>>>>>>>>>> from
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>> org.apache.nifi:nifi-provenance-repository-nar:1.13.0-SNAPSHOT
> >>>> but
> >>>>>>>>>>>>>>> that
> >>>>>>>>>>>>>>>>>> class name is already loaded/registered from
> >>>>>>>>>>>>>>>>>> org.apache.nifi:nifi-stateless-nar:1.13.0-SNAPSHOT and
> >>>>>>>>>>>> multiple
> >>>>>>>>>>>>>>> versions
> >>>>>>>>>>>>>>>>>> are not supported for this type
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>> These log messages appear just before the NAR extraction
> >>>>>>>>>>>> logs during
> >>>>>>>>>>>>>>>>>> instance startup.
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>> Don't know whether these are things that should be fixed
> >>>>>>>>>>>> before
> >>>>>>>>>>>>>>> 1.13.0
> >>>>>>>>>>>>>>>>>> and/or have already been looked into, but figured I'd
> >>>>>>>>>>>> mention them so
> >>>>>>>>>>>>>>>>>> they're at least known about.
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>> ---
> >>>>>>>>>>>>>>>>>> *Chris Sampson*
> >>>>>>>>>>>>>>>>>> IT Consultant
> >>>>>>>>>>>>>>>>>> chris.sampson@naimuri.com
> >>>>>>>>>>>>>>>>>> <https://www.naimuri.com/>
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>> On Mon, 30 Nov 2020 at 18:50, Nissim Shiman
> >>>>>>>>>>>>>>> <ns...@yahoo.com.invalid>
> >>>>>>>>>>>>>>>>>> wrote:
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>> Hello Nifi Team,
> >>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>> NIFI-7738 [1]
> >>>>>>>> https://github.com/apache/nifi/pull/4563
> >>>>>>>>>>>>>>>>>>> has already been reviewed/tested by a fellow
> >>>>>>>> contributer
> >>>>>>>>>>>>>>>>>>> I would greatly appreciate a committer moving this to
> >>>>>>>>> main
> >>>>>>>>>>>> for
> >>>>>>>>>>>>>>> 1.13.0
> >>>>>>>>>>>>>>>>>>> Thanks,
> >>>>>>>>>>>>>>>>>>> Nissim Shiman
> >>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>> [1] https://issues.apache.org/jira/browse/NIFI-7738
> >>>>>>>>>>>>>>>>>>> On Sunday, November 29, 2020, 07:12:12 PM EST, Matt
> >>>>>>>>>>>> Burgess <
> >>>>>>>>>>>>>>>>>>> mattyb149@apache.org> wrote:
> >>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>> I just merged Mike's Cassandra DMC PR, reviewing the
> >>>>>>>>>>>> graph stuff
> >>>>>>>>>>>>>>> now.
> >>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>> I have a bunch of open PRs [1], I don't think any are
> >>>>>>>>>>>> blockers for
> >>>>>>>>>>>>>>>>>>> 1.13.0 but thought I'd take this opportunity to find
> >>>>>>>> some
> >>>>>>>>>>>>>>> reviewers :)
> >>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>> Regards,
> >>>>>>>>>>>>>>>>>>> Matt
> >>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>> [1] https://github.com/apache/nifi/pulls/mattyb149
> >>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>> On Sat, Nov 28, 2020 at 10:13 AM Phillip Grenier
> >>>>>>>>>>>>>>> <ph...@nifi.rocks>
> >>>>>>>>>>>>>>>>>>> wrote:
> >>>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>>> I wouldn't mind
> >>>>>>>>> https://github.com/apache/nifi/pull/4554
> >>>>>>>>>>>> making
> >>>>>>>>>>>>>>> it
> >>>>>>>>>>>>>>>>> in.
> >>>>>>>>>>>>>>>>>>> Have
> >>>>>>>>>>>>>>>>>>>> seen a couple more instances where people have
> >>>>>>>> created
> >>>>>>>>>>>> custom
> >>>>>>>>>>>>>>>>> processors
> >>>>>>>>>>>>>>>>>>> to
> >>>>>>>>>>>>>>>>>>>> work around this PR.
> >>>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>>> On Thu, Nov 26, 2020 at 11:10 AM Mike Thomsen <
> >>>>>>>>>>>>>>>>> mikerthomsen@gmail.com>
> >>>>>>>>>>>>>>>>>>>> wrote:
> >>>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>>>> Also, for most of us (committers and community
> >>>>>>>>>>>> members), it's a
> >>>>>>>>>>>>>>>>>>>>> holiday season so might be good to delay a release
> >>>>>>>> to
> >>>>>>>>>>>> early
> >>>>>>>>>>>>>>> January
> >>>>>>>>>>>>>>>>>>>>> anyway. Just a thought.
> >>>>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>>>> On Thu, Nov 26, 2020 at 11:08 AM Mike Thomsen <
> >>>>>>>>>>>>>>>>> mikerthomsen@gmail.com>
> >>>>>>>>>>>>>>>>>>>>> wrote:
> >>>>>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>>>>> https://github.com/apache/nifi/pull/4638 - This
> >>>>>>>> is
> >>>>>>>>>>>> a big
> >>>>>>>>>>>>>>>>> increase in
> >>>>>>>>>>>>>>>>>>>>>> graph functionality, and I want to give him a
> >>>>>>>>> chance
> >>>>>>>>>>>> to get
> >>>>>>>>>>>>>>> his
> >>>>>>>>>>>>>>>>> first
> >>>>>>>>>>>>>>>>>>>>>> contribution in with 1.13 (we may have some more
> >>>>>>>> of
> >>>>>>>>>>>> his work
> >>>>>>>>>>>>>>> we
> >>>>>>>>>>>>>>>>> can
> >>>>>>>>>>>>>>>>>>>>>> open source).
> >>>>>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>>>>> Matt's also reviewing some of my Cassandra and
> >>>>>>>>> graph
> >>>>>>>>>>>> tickets
> >>>>>>>>>>>>>>> as
> >>>>>>>>>>>>>>>>> well.
> >>>>>>>>>>>>>>>>>>>>>> I wouldn't call those **blockers**, but having
> >>>>>>>> the
> >>>>>>>>>>>> Cassandra
> >>>>>>>>>>>>>>> DMC
> >>>>>>>>>>>>>>>>>>> fully
> >>>>>>>>>>>>>>>>>>>>>> fleshed out would be nice.
> >>>>>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>>>>> On Thu, Nov 26, 2020 at 9:10 AM Otto Fowler <
> >>>>>>>>>>>>>>>>> ottobackwards@gmail.com
> >>>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>>>> wrote:
> >>>>>>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>>>>>> NIFI-7795
> >>>>>>>>>>>> https://github.com/apache/nifi/pull/4656
> >>>>>>>>>>>>>>>>>>>>>>> NIFI-7761
> >>>>>>>>> https://github.com/apache/nifi/pull/4513
> >>>>>>>>>>>>>>>>>>>>>>> NIFI-2072
> >>>>>>>>> https://github.com/apache/nifi/pull/4384
> >>>>>>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>>>>>> From: Pierre Villard <
> >>>>>>>>> pierre.villard.fr@gmail.com>
> >>>>>>>>>>>>>>>>>>>>>>> <pi...@gmail.com>
> >>>>>>>>>>>>>>>>>>>>>>> Reply: dev@nifi.apache.org <
> >>>>>>>> dev@nifi.apache.org>
> >>>>>>>>> <
> >>>>>>>>>>>>>>>>>>> dev@nifi.apache.org>
> >>>>>>>>>>>>>>>>>>>>>>> Date: November 26, 2020 at 04:55:56
> >>>>>>>>>>>>>>>>>>>>>>> To: dev@nifi.apache.org <de...@nifi.apache.org>
> >>>>>>>> <
> >>>>>>>>>>>>>>>>> dev@nifi.apache.org
> >>>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>>>>>> Subject: [DISCUSS] Release of Apache NiFi
> >>>>>>>> 1.13.0
> >>>>>>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>>>>>> Hi community,
> >>>>>>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>>>>>> Starting a discussion thread around the release
> >>>>>>>>> of
> >>>>>>>>>>>> NiFi
> >>>>>>>>>>>>>>>>> 1.13.0. We
> >>>>>>>>>>>>>>>>>>>>> added
> >>>>>>>>>>>>>>>>>>>>>>> quite a lot of significant improvements and
> >>>>>>>>>>>> features since
> >>>>>>>>>>>>>>> the
> >>>>>>>>>>>>>>>>>>> release
> >>>>>>>>>>>>>>>>>>>>> of
> >>>>>>>>>>>>>>>>>>>>>>> 1.12.1 - I see 143 JIRAs with 1.13.0 as the fix
> >>>>>>>>>>>> version. I
> >>>>>>>>>>>>>>>>> think it
> >>>>>>>>>>>>>>>>>>>>> makes
> >>>>>>>>>>>>>>>>>>>>>>> sense to consider a new release.
> >>>>>>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>>>>>> Please share here the JIRAs with opened pull
> >>>>>>>>>>>> requests that
> >>>>>>>>>>>>>>> we
> >>>>>>>>>>>>>>>>> would
> >>>>>>>>>>>>>>>>>>>>> need to
> >>>>>>>>>>>>>>>>>>>>>>> look at to make this release happen.
> >>>>>>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>>>>>> Thanks,
> >>>>>>>>>>>>>>>>>>>>>>> Pierre
> >>>>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>
> >>>>>>>>
> >>>>>>
> >>>>>>
> >>>>
> >>>>
>
Re: [DISCUSS] Release of Apache NiFi 1.13.0
Posted by Joey Frazee <jo...@icloud.com.INVALID>.
You’ve fixed it now by removing it, but I took a look at the history and that module just wasn’t a dependency of anything anymore and the release plugin doesn’t automatically update the version in that case.
I think the RM guidance might just be “check that <version /> was correctly updated” to catch this when it might matter.
-joey
> On Feb 1, 2021, at 1:33 PM, Joe Witt <jo...@gmail.com> wrote:
>
> Team
>
> starting RC2. Joey Frazee noted "I noticed that
> nifi-docker/dockermaven-stateless/pom.xml
> and nifi-docker/docker-compose/docker-compose.yml in the source package and
> tag are still using 1.13.0-SNAPSHOT" while looking at RC1. I have no
> instructions/guidance on what to do with those as an RM and I've never
> modified them before. If we're going to keep these in the build, and I
> would advocate actually that we remove them, then someone needs to
> determine the whole lifecycle of how to manage/maintain them and
> document the steps for a RelMgr. The dockerhub module we do have guidance
> for and they're currently correct.
>
> Thanks
>
>> On Mon, Feb 1, 2021 at 10:14 AM Joe Witt <jo...@gmail.com> wrote:
>>
>> Team,
>>
>> Will put RC2 for 1.13 back up today hopefully. The fix is in for the
>> issue that sank the release.
>>
>> Thanks
>> Joe
>>
>>> On Thu, Jan 28, 2021 at 8:18 AM Joe Witt <jo...@gmail.com> wrote:
>>>
>>> Otto
>>>
>>> Truth is we dont know. We cannot readily test with the amazing matrix
>>> that exists. So we are leaning toward ensuring recent versions work as
>>> expected.
>>>
>>> The goal is java 8 and 11 broadly right now. But these internal changes
>>> of exception types being used are brutal.
>>>
>>> Thanks
>>>
>>> On Thu, Jan 28, 2021 at 8:15 AM Otto Fowler <ot...@gmail.com>
>>> wrote:
>>>
>>>> Thanks Joe,
>>>>
>>>> I’m started down that road right after I sent this. I’ll update when I
>>>> know.
>>>> I _have_ been building nifi with this jdk all along though.
>>>>
>>>> If there are jdk minimum requirements, should they be documented ( or
>>>> are they and I missed it)?
>>>>
>>>>> On Jan 28, 2021, at 09:35, Joe Witt <jo...@gmail.com> wrote:
>>>>>
>>>>> Otto
>>>>>
>>>>> I dont know we can keep all variants of Java 8 happy. That one is
>>>> nearly
>>>>> three years old. I would say try with something more recent. It has
>>>> been
>>>>> pretty shocking how many api changes we have seen across these builds.
>>>>>
>>>>> Thanks
>>>>>
>>>>> On Thu, Jan 28, 2021 at 6:12 AM Otto Fowler <ot...@gmail.com>
>>>> wrote:
>>>>>
>>>>>> I’m trying to validate RC-1 and I’m seeing this exception building /
>>>>>> running tests
>>>>>>
>>>>>> [INFO] Running org.apache.nifi.processors.standard.TestListenTCP
>>>>>> [ERROR] Tests run: 6, Failures: 1, Errors: 0, Skipped: 0, Time
>>>> elapsed:
>>>>>> 4.499 s <<< FAILURE! - in
>>>> org.apache.nifi.processors.standard.TestListenTCP
>>>>>> [ERROR]
>>>>>>
>>>> testTLSClientAuthRequiredAndClientCertNotProvided(org.apache.nifi.processors.standard.TestListenTCP)
>>>>>> Time elapsed: 0.127 s <<< FAILURE!
>>>>>> java.lang.AssertionError: unexpected exception type thrown;
>>>>>> expected:<javax.net.ssl.SSLException> but
>>>> was:<java.net.SocketException>
>>>>>> at
>>>>>>
>>>> org.apache.nifi.processors.standard.TestListenTCP.testTLSClientAuthRequiredAndClientCertNotProvided(TestListenTCP.java:159)
>>>>>> Caused by: java.net.SocketException: Connection reset
>>>>>> at
>>>>>>
>>>> org.apache.nifi.processors.standard.TestListenTCP.runTCP(TestListenTCP.java:209)
>>>>>> at
>>>>>>
>>>> org.apache.nifi.processors.standard.TestListenTCP.lambda$testTLSClientAuthRequiredAndClientCertNotProvided$0(TestListenTCP.java:160)
>>>>>> at
>>>>>>
>>>> org.apache.nifi.processors.standard.TestListenTCP.testTLSClientAuthRequiredAndClientCertNotProvided(TestListenTCP.java:159)
>>>>>>
>>>>>>
>>>>>>
>>>>>> Apache Maven 3.6.3 (cecedd343002696d0abb50b32b541b8a6ba2883f)
>>>>>> Maven home: /usr/local/Cellar/maven/3.6.3_1/libexec
>>>>>> Java version: 1.8.0_171, vendor: Oracle Corporation, runtime:
>>>>>> /Library/Java/JavaVirtualMachines/jdk1.8.0_171.jdk/Contents/Home/jre
>>>>>> Default locale: en_US, platform encoding: UTF-8
>>>>>> OS name: "mac os x", version: "10.16", arch: "x86_64", family: “mac"
>>>>>>
>>>>>>
>>>>>>
>>>>>>> On Jan 27, 2021, at 10:31, Joe Witt <jo...@gmail.com> wrote:
>>>>>>>
>>>>>>> ...in this brutal game of wach a mole another couple brittle tests
>>>> have
>>>>>>> emerged on the Java 11 line.
>>>>>>> https://issues.apache.org/jira/browse/NIFI-8177 will get that looked
>>>>>> into.
>>>>>>> And I'm also seeing if for some reason adding a bit more
>>>> horsepower/cpu
>>>>>>> usage to the github tests will help. Things had been very stable for
>>>>>> quite
>>>>>>> a while until the update to the latest 11.0.10 azul jdk came out so
>>>> kind
>>>>>> of
>>>>>>> strange the tests became less reliable then. Anyway dont want to
>>>> initiate
>>>>>>> the RC until things seem stable otherwise it makes the vote process
>>>> more
>>>>>>> difficult and further when the builds dont pass it makes the already
>>>>>>> difficult task of staying apace with PRs more inivolved.
>>>>>>>
>>>>>>> Thanks
>>>>>>>
>>>>>>> On Wed, Jan 27, 2021 at 12:19 AM Pierre Villard <
>>>>>> pierre.villard.fr@gmail.com>
>>>>>>> wrote:
>>>>>>>
>>>>>>>> Awesome, thanks Joe!
>>>>>>>>
>>>>>>>> Le mer. 27 janv. 2021 à 10:16, Joe Witt <jo...@gmail.com> a
>>>> écrit :
>>>>>>>>
>>>>>>>>> Team,
>>>>>>>>>
>>>>>>>>> Ok wow so the issue with build failures that emerged has been
>>>> resolved
>>>>>> it
>>>>>>>>> appears thanks to a lot of effort by exceptionfactory. The other
>>>>>>>> lingering
>>>>>>>>> commits/PRs are in and I think most of what folks asked for in this
>>>>>>>>> thread. I just put in a commit which drops a few older/less common
>>>>>> nars
>>>>>>>>> from convenience binary inclusion to get us back under the maximum
>>>> size
>>>>>>>>> again. And now I think we can initiate RC1 build for 1.13.0.
>>>>>>>>>
>>>>>>>>> That should be published in the AM.
>>>>>>>>>
>>>>>>>>> Thanks
>>>>>>>>>
>>>>>>>>> On Mon, Jan 25, 2021 at 6:40 AM Joe Witt <jo...@gmail.com>
>>>> wrote:
>>>>>>>>>
>>>>>>>>>> Team,
>>>>>>>>>>
>>>>>>>>>> There is a TZ handling issue
>>>>>>>>>> https://issues.apache.org/jira/browse/NIFI-8023 that needs a
>>>>>>>> resolution
>>>>>>>>>> and there is also a new issue that has emerged on Github
>>>> Actions/CI
>>>>>>>>>> https://github.com/apache/nifi/actions which is resulting in
>>>> broken
>>>>>>>>>> builds. This emerged in the latest Java 11 Azul release and in
>>>> Github
>>>>>>>>> CI.
>>>>>>>>>> I've tried to replicate with no success on a local linux machine
>>>> with
>>>>>>>> the
>>>>>>>>>> exact same JVM/version.
>>>>>>>>>>
>>>>>>>>>> Once these are wrapped I'll initiate the RC. Great work to all
>>>>>>>> involved
>>>>>>>>>> in helping get the release candidate this close.
>>>>>>>>>>
>>>>>>>>>> Thanks
>>>>>>>>>> Joe
>>>>>>>>>>
>>>>>>>>>> On Thu, Jan 21, 2021 at 8:30 AM Joe Witt <jo...@gmail.com>
>>>> wrote:
>>>>>>>>>>
>>>>>>>>>>> Team,
>>>>>>>>>>>
>>>>>>>>>>> A couple 1.13 tagged items still lingering. Going to either kick
>>>>>> them
>>>>>>>>>>> out or merge them and get going. Hopefully an RC today or
>>>> tomorrow.
>>>>>>>>>>>
>>>>>>>>>>> Thanks
>>>>>>>>>>>
>>>>>>>>>>> On Wed, Jan 20, 2021 at 7:21 AM Mike Thomsen <
>>>> mikerthomsen@gmail.com
>>>>>>>
>>>>>>>>>>> wrote:
>>>>>>>>>>>
>>>>>>>>>>>> Bug confirmed. Working on a PR now.
>>>>>>>>>>>>
>>>>>>>>>>>> On Wed, Jan 20, 2021 at 8:45 AM Mike Thomsen <
>>>>>> mikerthomsen@gmail.com
>>>>>>>>>
>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>> This morning, I think I found a serious bug in
>>>> PutCassandraRecord
>>>>>>>> WRT
>>>>>>>>>>>>> writing binary data to Cassandra. I'm debugging now. If it's
>>>>>>>> really a
>>>>>>>>>>>>> bug, I'd appreciate it if we could squeak a fix into 1.13.
>>>>>>>>>>>>>
>>>>>>>>>>>>> On Tue, Jan 19, 2021 at 9:54 AM Joe Witt <jo...@gmail.com>
>>>>>>>> wrote:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Team,
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> I'm going to initiate RM processes for 1.13. I'll be watching
>>>>>>>>>>>> closely for
>>>>>>>>>>>>>> currently tagged 1.13 items to include. If anything is
>>>> dragging
>>>>>>>>>>>> I'll just
>>>>>>>>>>>>>> remove it from 1.13 and we'll pick it up later. Other items
>>>> that
>>>>>>>>> get
>>>>>>>>>>>>>> dev/reviewer traction before I cut the RC we can include. I
>>>> will
>>>>>>>>>>>>>> *probably/hopefully* start that process first thing tomorrow
>>>>>>>>> morning.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>> https://issues.apache.org/jira/projects/NIFI/versions/12348700
>>>>>>>> is
>>>>>>>>>>>> what i'm
>>>>>>>>>>>>>> working from.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Thanks
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> On Fri, Jan 15, 2021 at 6:12 PM Waleed Aibany <
>>>>>>>> walmut44@gmail.com>
>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Hi,
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> I did rebase to this old PR
>>>>>>>>>>>> https://github.com/apache/nifi/pull/4167
>>>>>>>>>>>>>>> Is it possible to include it in 1.13.0
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Thank you
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> On 2021/01/05 15:03:32, Pierre Villard <
>>>>>>>>>>>> pierre.villard.fr@gmail.com>
>>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>> Hi all,
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Happy new year to everyone, hope you all had a great time.
>>>>>>>> I'm
>>>>>>>>>>>> bumping
>>>>>>>>>>>>>>> this
>>>>>>>>>>>>>>>> thread up as I think it'd make a lot of sense to release
>>>> NiFi
>>>>>>>>>>>> 1.13.0. We
>>>>>>>>>>>>>>>> have a ton of bug fixes and improvements that would be very
>>>>>>>>>>>> useful for
>>>>>>>>>>>>>>> our
>>>>>>>>>>>>>>>> community.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Let's try to see if there are any blockers for a release and
>>>>>>>>>>>> start the
>>>>>>>>>>>>>>>> process:
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>
>>>> https://issues.apache.org/jira/issues/?jql=project%20%3D%20NIFI%20AND%20resolution%20%3D%20Unresolved%20AND%20fixVersion%20%3D%201.13.0%20ORDER%20BY%20priority%20DESC%2C%20updated%20DESC
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Thanks!
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Le mar. 1 déc. 2020 à 14:49, Bryan Bende <bb...@gmail.com>
>>>>>>>> a
>>>>>>>>>>>> écrit :
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Chris,
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> The illegal reflective access warnings are expected when
>>>>>>>>>>>> running on
>>>>>>>>>>>>>>> Java
>>>>>>>>>>>>>>>>> 11.
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> The second warning about the provenance repo seems like a
>>>>>>>>>>>> possible
>>>>>>>>>>>>>>>>> issue due to some recent refactorings made for stateless,
>>>>>>>> we
>>>>>>>>>>>> should
>>>>>>>>>>>>>>>>> take a look at that.
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Thanks,
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Bryan
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> On Tue, Dec 1, 2020 at 3:58 AM Chris Sampson
>>>>>>>>>>>>>>>>> <ch...@naimuri.com.invalid> wrote:
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> Just spotted the following during startup of NiFi
>>>>>>>>>>>> 1.13.0-SNAPSHOT on
>>>>>>>>>>>>>>> my
>>>>>>>>>>>>>>>>>> local machine, which might be worth looking at (although
>>>>>>>>>>>> I've not
>>>>>>>>>>>>>>> deleted
>>>>>>>>>>>>>>>>>> and re-created the binaries in a little while, so I could
>>>>>>>>>>>> have
>>>>>>>>>>>>>>> something
>>>>>>>>>>>>>>>>>> wrong in my /lib folder or such):
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> 2020-12-01 08:52:48,382 ERROR [NiFi logging handler]
>>>>>>>>>>>>>>>>> org.apache.nifi.StdErr
>>>>>>>>>>>>>>>>>> WARNING: An illegal reflective access operation has
>>>>>>>>> occurred
>>>>>>>>>>>>>>>>>> 2020-12-01 08:52:48,383 ERROR [NiFi logging handler]
>>>>>>>>>>>>>>>>> org.apache.nifi.StdErr
>>>>>>>>>>>>>>>>>> WARNING: Illegal reflective access by
>>>>>>>>>>>>>>>>>> com.sun.xml.bind.v2.runtime.reflect.opt.Injector
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>> (file:.../nifi-1.13.0-SNAPSHOT/lib/java11/jaxb-impl-2.3.0.jar)
>>>> to
>>>>>>>>>>>>>>> method
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>> java.lang.ClassLoader.defineClass(java.lang.String,byte[],int,int)
>>>>>>>>>>>>>>>>>> 2020-12-01 08:52:48,383 ERROR [NiFi logging handler]
>>>>>>>>>>>>>>>>> org.apache.nifi.StdErr
>>>>>>>>>>>>>>>>>> WARNING: Please consider reporting this to the
>>>>>>>> maintainers
>>>>>>>>> of
>>>>>>>>>>>>>>>>>> com.sun.xml.bind.v2.runtime.reflect.opt.Injector
>>>>>>>>>>>>>>>>>> 2020-12-01 08:52:48,383 ERROR [NiFi logging handler]
>>>>>>>>>>>>>>>>> org.apache.nifi.StdErr
>>>>>>>>>>>>>>>>>> WARNING: Use --illegal-access=warn to enable warnings of
>>>>>>>>>>>> further
>>>>>>>>>>>>>>> illegal
>>>>>>>>>>>>>>>>>> reflective access operations
>>>>>>>>>>>>>>>>>> 2020-12-01 08:52:48,383 ERROR [NiFi logging handler]
>>>>>>>>>>>>>>>>> org.apache.nifi.StdErr
>>>>>>>>>>>>>>>>>> WARNING: All illegal access operations will be denied in
>>>>>>>> a
>>>>>>>>>>>> future
>>>>>>>>>>>>>>> release
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> Also:
>>>>>>>>>>>>>>>>>> 2020-12-01 08:52:52,486 WARN [main]
>>>>>>>>>>>>>>>>>> o.a.n.n.StandardExtensionDiscoveringManager Failed to
>>>>>>>>>>>> register
>>>>>>>>>>>>>>> extension
>>>>>>>>>>>>>>>>>> org.apache.nifi.provenance.VolatileProvenanceRepository
>>>>>>>> due
>>>>>>>>>>>> to:
>>>>>>>>>>>>>>> Attempt
>>>>>>>>>>>>>>>>> was
>>>>>>>>>>>>>>>>>> made to load
>>>>>>>>>>>> org.apache.nifi.provenance.VolatileProvenanceRepository
>>>>>>>>>>>>>>> from
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>> org.apache.nifi:nifi-provenance-repository-nar:1.13.0-SNAPSHOT
>>>> but
>>>>>>>>>>>>>>> that
>>>>>>>>>>>>>>>>>> class name is already loaded/registered from
>>>>>>>>>>>>>>>>>> org.apache.nifi:nifi-stateless-nar:1.13.0-SNAPSHOT and
>>>>>>>>>>>> multiple
>>>>>>>>>>>>>>> versions
>>>>>>>>>>>>>>>>>> are not supported for this type
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> These log messages appear just before the NAR extraction
>>>>>>>>>>>> logs during
>>>>>>>>>>>>>>>>>> instance startup.
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> Don't know whether these are things that should be fixed
>>>>>>>>>>>> before
>>>>>>>>>>>>>>> 1.13.0
>>>>>>>>>>>>>>>>>> and/or have already been looked into, but figured I'd
>>>>>>>>>>>> mention them so
>>>>>>>>>>>>>>>>>> they're at least known about.
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> ---
>>>>>>>>>>>>>>>>>> *Chris Sampson*
>>>>>>>>>>>>>>>>>> IT Consultant
>>>>>>>>>>>>>>>>>> chris.sampson@naimuri.com
>>>>>>>>>>>>>>>>>> <https://www.naimuri.com/>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> On Mon, 30 Nov 2020 at 18:50, Nissim Shiman
>>>>>>>>>>>>>>> <ns...@yahoo.com.invalid>
>>>>>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> Hello Nifi Team,
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> NIFI-7738 [1]
>>>>>>>> https://github.com/apache/nifi/pull/4563
>>>>>>>>>>>>>>>>>>> has already been reviewed/tested by a fellow
>>>>>>>> contributer
>>>>>>>>>>>>>>>>>>> I would greatly appreciate a committer moving this to
>>>>>>>>> main
>>>>>>>>>>>> for
>>>>>>>>>>>>>>> 1.13.0
>>>>>>>>>>>>>>>>>>> Thanks,
>>>>>>>>>>>>>>>>>>> Nissim Shiman
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> [1] https://issues.apache.org/jira/browse/NIFI-7738
>>>>>>>>>>>>>>>>>>> On Sunday, November 29, 2020, 07:12:12 PM EST, Matt
>>>>>>>>>>>> Burgess <
>>>>>>>>>>>>>>>>>>> mattyb149@apache.org> wrote:
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> I just merged Mike's Cassandra DMC PR, reviewing the
>>>>>>>>>>>> graph stuff
>>>>>>>>>>>>>>> now.
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> I have a bunch of open PRs [1], I don't think any are
>>>>>>>>>>>> blockers for
>>>>>>>>>>>>>>>>>>> 1.13.0 but thought I'd take this opportunity to find
>>>>>>>> some
>>>>>>>>>>>>>>> reviewers :)
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> Regards,
>>>>>>>>>>>>>>>>>>> Matt
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> [1] https://github.com/apache/nifi/pulls/mattyb149
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> On Sat, Nov 28, 2020 at 10:13 AM Phillip Grenier
>>>>>>>>>>>>>>> <ph...@nifi.rocks>
>>>>>>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> I wouldn't mind
>>>>>>>>> https://github.com/apache/nifi/pull/4554
>>>>>>>>>>>> making
>>>>>>>>>>>>>>> it
>>>>>>>>>>>>>>>>> in.
>>>>>>>>>>>>>>>>>>> Have
>>>>>>>>>>>>>>>>>>>> seen a couple more instances where people have
>>>>>>>> created
>>>>>>>>>>>> custom
>>>>>>>>>>>>>>>>> processors
>>>>>>>>>>>>>>>>>>> to
>>>>>>>>>>>>>>>>>>>> work around this PR.
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> On Thu, Nov 26, 2020 at 11:10 AM Mike Thomsen <
>>>>>>>>>>>>>>>>> mikerthomsen@gmail.com>
>>>>>>>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> Also, for most of us (committers and community
>>>>>>>>>>>> members), it's a
>>>>>>>>>>>>>>>>>>>>> holiday season so might be good to delay a release
>>>>>>>> to
>>>>>>>>>>>> early
>>>>>>>>>>>>>>> January
>>>>>>>>>>>>>>>>>>>>> anyway. Just a thought.
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> On Thu, Nov 26, 2020 at 11:08 AM Mike Thomsen <
>>>>>>>>>>>>>>>>> mikerthomsen@gmail.com>
>>>>>>>>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> https://github.com/apache/nifi/pull/4638 - This
>>>>>>>> is
>>>>>>>>>>>> a big
>>>>>>>>>>>>>>>>> increase in
>>>>>>>>>>>>>>>>>>>>>> graph functionality, and I want to give him a
>>>>>>>>> chance
>>>>>>>>>>>> to get
>>>>>>>>>>>>>>> his
>>>>>>>>>>>>>>>>> first
>>>>>>>>>>>>>>>>>>>>>> contribution in with 1.13 (we may have some more
>>>>>>>> of
>>>>>>>>>>>> his work
>>>>>>>>>>>>>>> we
>>>>>>>>>>>>>>>>> can
>>>>>>>>>>>>>>>>>>>>>> open source).
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> Matt's also reviewing some of my Cassandra and
>>>>>>>>> graph
>>>>>>>>>>>> tickets
>>>>>>>>>>>>>>> as
>>>>>>>>>>>>>>>>> well.
>>>>>>>>>>>>>>>>>>>>>> I wouldn't call those **blockers**, but having
>>>>>>>> the
>>>>>>>>>>>> Cassandra
>>>>>>>>>>>>>>> DMC
>>>>>>>>>>>>>>>>>>> fully
>>>>>>>>>>>>>>>>>>>>>> fleshed out would be nice.
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> On Thu, Nov 26, 2020 at 9:10 AM Otto Fowler <
>>>>>>>>>>>>>>>>> ottobackwards@gmail.com
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>> NIFI-7795
>>>>>>>>>>>> https://github.com/apache/nifi/pull/4656
>>>>>>>>>>>>>>>>>>>>>>> NIFI-7761
>>>>>>>>> https://github.com/apache/nifi/pull/4513
>>>>>>>>>>>>>>>>>>>>>>> NIFI-2072
>>>>>>>>> https://github.com/apache/nifi/pull/4384
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>> From: Pierre Villard <
>>>>>>>>> pierre.villard.fr@gmail.com>
>>>>>>>>>>>>>>>>>>>>>>> <pi...@gmail.com>
>>>>>>>>>>>>>>>>>>>>>>> Reply: dev@nifi.apache.org <
>>>>>>>> dev@nifi.apache.org>
>>>>>>>>> <
>>>>>>>>>>>>>>>>>>> dev@nifi.apache.org>
>>>>>>>>>>>>>>>>>>>>>>> Date: November 26, 2020 at 04:55:56
>>>>>>>>>>>>>>>>>>>>>>> To: dev@nifi.apache.org <de...@nifi.apache.org>
>>>>>>>> <
>>>>>>>>>>>>>>>>> dev@nifi.apache.org
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>> Subject: [DISCUSS] Release of Apache NiFi
>>>>>>>> 1.13.0
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>> Hi community,
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>> Starting a discussion thread around the release
>>>>>>>>> of
>>>>>>>>>>>> NiFi
>>>>>>>>>>>>>>>>> 1.13.0. We
>>>>>>>>>>>>>>>>>>>>> added
>>>>>>>>>>>>>>>>>>>>>>> quite a lot of significant improvements and
>>>>>>>>>>>> features since
>>>>>>>>>>>>>>> the
>>>>>>>>>>>>>>>>>>> release
>>>>>>>>>>>>>>>>>>>>> of
>>>>>>>>>>>>>>>>>>>>>>> 1.12.1 - I see 143 JIRAs with 1.13.0 as the fix
>>>>>>>>>>>> version. I
>>>>>>>>>>>>>>>>> think it
>>>>>>>>>>>>>>>>>>>>> makes
>>>>>>>>>>>>>>>>>>>>>>> sense to consider a new release.
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>> Please share here the JIRAs with opened pull
>>>>>>>>>>>> requests that
>>>>>>>>>>>>>>> we
>>>>>>>>>>>>>>>>> would
>>>>>>>>>>>>>>>>>>>>> need to
>>>>>>>>>>>>>>>>>>>>>>> look at to make this release happen.
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>> Thanks,
>>>>>>>>>>>>>>>>>>>>>>> Pierre
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>
>>>>>>
>>>>
>>>>
Re: [DISCUSS] Release of Apache NiFi 1.13.0
Posted by Joe Witt <jo...@gmail.com>.
nifi-framework-bundle/nifi-framework/nifi-stateless is gone. I think you
just need to clean your repo.
The other two I think are defunct and I'll delete right now.
Thanks
On Mon, Feb 1, 2021 at 2:56 PM Mark Bean <ma...@gmail.com> wrote:
> Today, I also noticed that the following modules still have code in them.
> However, they are not listed as a module in the corresponding pom.xml.
>
> nifi-docker/docker-compose
> nifi-docker/dockermaven-stateless
> nifi-framework-bundle/nifi-framework/nifi-stateless
>
> Is this dead code that should simply be removed? Also, I did not email this
> out yet because I did not finish searching the codebase for other such
> "unused" code.
>
> At a minimum, as best I can tell, the above can be removed entirely.
>
> -Mark
>
>
>
> On Mon, Feb 1, 2021 at 4:33 PM Joe Witt <jo...@gmail.com> wrote:
>
> > Team
> >
> > starting RC2. Joey Frazee noted "I noticed that
> > nifi-docker/dockermaven-stateless/pom.xml
> > and nifi-docker/docker-compose/docker-compose.yml in the source package
> and
> > tag are still using 1.13.0-SNAPSHOT" while looking at RC1. I have no
> > instructions/guidance on what to do with those as an RM and I've never
> > modified them before. If we're going to keep these in the build, and I
> > would advocate actually that we remove them, then someone needs to
> > determine the whole lifecycle of how to manage/maintain them and
> > document the steps for a RelMgr. The dockerhub module we do have
> guidance
> > for and they're currently correct.
> >
> > Thanks
> >
> > On Mon, Feb 1, 2021 at 10:14 AM Joe Witt <jo...@gmail.com> wrote:
> >
> > > Team,
> > >
> > > Will put RC2 for 1.13 back up today hopefully. The fix is in for the
> > > issue that sank the release.
> > >
> > > Thanks
> > > Joe
> > >
> > > On Thu, Jan 28, 2021 at 8:18 AM Joe Witt <jo...@gmail.com> wrote:
> > >
> > >> Otto
> > >>
> > >> Truth is we dont know. We cannot readily test with the amazing matrix
> > >> that exists. So we are leaning toward ensuring recent versions work
> as
> > >> expected.
> > >>
> > >> The goal is java 8 and 11 broadly right now. But these internal
> changes
> > >> of exception types being used are brutal.
> > >>
> > >> Thanks
> > >>
> > >> On Thu, Jan 28, 2021 at 8:15 AM Otto Fowler <ot...@gmail.com>
> > >> wrote:
> > >>
> > >>> Thanks Joe,
> > >>>
> > >>> I’m started down that road right after I sent this. I’ll update
> when I
> > >>> know.
> > >>> I _have_ been building nifi with this jdk all along though.
> > >>>
> > >>> If there are jdk minimum requirements, should they be documented ( or
> > >>> are they and I missed it)?
> > >>>
> > >>> > On Jan 28, 2021, at 09:35, Joe Witt <jo...@gmail.com> wrote:
> > >>> >
> > >>> > Otto
> > >>> >
> > >>> > I dont know we can keep all variants of Java 8 happy. That one is
> > >>> nearly
> > >>> > three years old. I would say try with something more recent. It
> has
> > >>> been
> > >>> > pretty shocking how many api changes we have seen across these
> > builds.
> > >>> >
> > >>> > Thanks
> > >>> >
> > >>> > On Thu, Jan 28, 2021 at 6:12 AM Otto Fowler <
> ottobackwards@gmail.com
> > >
> > >>> wrote:
> > >>> >
> > >>> >> I’m trying to validate RC-1 and I’m seeing this exception
> building /
> > >>> >> running tests
> > >>> >>
> > >>> >> [INFO] Running org.apache.nifi.processors.standard.TestListenTCP
> > >>> >> [ERROR] Tests run: 6, Failures: 1, Errors: 0, Skipped: 0, Time
> > >>> elapsed:
> > >>> >> 4.499 s <<< FAILURE! - in
> > >>> org.apache.nifi.processors.standard.TestListenTCP
> > >>> >> [ERROR]
> > >>> >>
> > >>>
> >
> testTLSClientAuthRequiredAndClientCertNotProvided(org.apache.nifi.processors.standard.TestListenTCP)
> > >>> >> Time elapsed: 0.127 s <<< FAILURE!
> > >>> >> java.lang.AssertionError: unexpected exception type thrown;
> > >>> >> expected:<javax.net.ssl.SSLException> but
> > >>> was:<java.net.SocketException>
> > >>> >> at
> > >>> >>
> > >>>
> >
> org.apache.nifi.processors.standard.TestListenTCP.testTLSClientAuthRequiredAndClientCertNotProvided(TestListenTCP.java:159)
> > >>> >> Caused by: java.net.SocketException: Connection reset
> > >>> >> at
> > >>> >>
> > >>>
> >
> org.apache.nifi.processors.standard.TestListenTCP.runTCP(TestListenTCP.java:209)
> > >>> >> at
> > >>> >>
> > >>>
> >
> org.apache.nifi.processors.standard.TestListenTCP.lambda$testTLSClientAuthRequiredAndClientCertNotProvided$0(TestListenTCP.java:160)
> > >>> >> at
> > >>> >>
> > >>>
> >
> org.apache.nifi.processors.standard.TestListenTCP.testTLSClientAuthRequiredAndClientCertNotProvided(TestListenTCP.java:159)
> > >>> >>
> > >>> >>
> > >>> >>
> > >>> >> Apache Maven 3.6.3 (cecedd343002696d0abb50b32b541b8a6ba2883f)
> > >>> >> Maven home: /usr/local/Cellar/maven/3.6.3_1/libexec
> > >>> >> Java version: 1.8.0_171, vendor: Oracle Corporation, runtime:
> > >>> >>
> /Library/Java/JavaVirtualMachines/jdk1.8.0_171.jdk/Contents/Home/jre
> > >>> >> Default locale: en_US, platform encoding: UTF-8
> > >>> >> OS name: "mac os x", version: "10.16", arch: "x86_64", family:
> “mac"
> > >>> >>
> > >>> >>
> > >>> >>
> > >>> >>> On Jan 27, 2021, at 10:31, Joe Witt <jo...@gmail.com> wrote:
> > >>> >>>
> > >>> >>> ...in this brutal game of wach a mole another couple brittle
> tests
> > >>> have
> > >>> >>> emerged on the Java 11 line.
> > >>> >>> https://issues.apache.org/jira/browse/NIFI-8177 will get that
> > looked
> > >>> >> into.
> > >>> >>> And I'm also seeing if for some reason adding a bit more
> > >>> horsepower/cpu
> > >>> >>> usage to the github tests will help. Things had been very stable
> > for
> > >>> >> quite
> > >>> >>> a while until the update to the latest 11.0.10 azul jdk came out
> so
> > >>> kind
> > >>> >> of
> > >>> >>> strange the tests became less reliable then. Anyway dont want to
> > >>> initiate
> > >>> >>> the RC until things seem stable otherwise it makes the vote
> process
> > >>> more
> > >>> >>> difficult and further when the builds dont pass it makes the
> > already
> > >>> >>> difficult task of staying apace with PRs more inivolved.
> > >>> >>>
> > >>> >>> Thanks
> > >>> >>>
> > >>> >>> On Wed, Jan 27, 2021 at 12:19 AM Pierre Villard <
> > >>> >> pierre.villard.fr@gmail.com>
> > >>> >>> wrote:
> > >>> >>>
> > >>> >>>> Awesome, thanks Joe!
> > >>> >>>>
> > >>> >>>> Le mer. 27 janv. 2021 à 10:16, Joe Witt <jo...@gmail.com> a
> > >>> écrit :
> > >>> >>>>
> > >>> >>>>> Team,
> > >>> >>>>>
> > >>> >>>>> Ok wow so the issue with build failures that emerged has been
> > >>> resolved
> > >>> >> it
> > >>> >>>>> appears thanks to a lot of effort by exceptionfactory. The
> other
> > >>> >>>> lingering
> > >>> >>>>> commits/PRs are in and I think most of what folks asked for in
> > this
> > >>> >>>>> thread. I just put in a commit which drops a few older/less
> > common
> > >>> >> nars
> > >>> >>>>> from convenience binary inclusion to get us back under the
> > maximum
> > >>> size
> > >>> >>>>> again. And now I think we can initiate RC1 build for 1.13.0.
> > >>> >>>>>
> > >>> >>>>> That should be published in the AM.
> > >>> >>>>>
> > >>> >>>>> Thanks
> > >>> >>>>>
> > >>> >>>>> On Mon, Jan 25, 2021 at 6:40 AM Joe Witt <jo...@gmail.com>
> > >>> wrote:
> > >>> >>>>>
> > >>> >>>>>> Team,
> > >>> >>>>>>
> > >>> >>>>>> There is a TZ handling issue
> > >>> >>>>>> https://issues.apache.org/jira/browse/NIFI-8023 that needs a
> > >>> >>>> resolution
> > >>> >>>>>> and there is also a new issue that has emerged on Github
> > >>> Actions/CI
> > >>> >>>>>> https://github.com/apache/nifi/actions which is resulting in
> > >>> broken
> > >>> >>>>>> builds. This emerged in the latest Java 11 Azul release and
> in
> > >>> Github
> > >>> >>>>> CI.
> > >>> >>>>>> I've tried to replicate with no success on a local linux
> machine
> > >>> with
> > >>> >>>> the
> > >>> >>>>>> exact same JVM/version.
> > >>> >>>>>>
> > >>> >>>>>> Once these are wrapped I'll initiate the RC. Great work to
> all
> > >>> >>>> involved
> > >>> >>>>>> in helping get the release candidate this close.
> > >>> >>>>>>
> > >>> >>>>>> Thanks
> > >>> >>>>>> Joe
> > >>> >>>>>>
> > >>> >>>>>> On Thu, Jan 21, 2021 at 8:30 AM Joe Witt <jo...@gmail.com>
> > >>> wrote:
> > >>> >>>>>>
> > >>> >>>>>>> Team,
> > >>> >>>>>>>
> > >>> >>>>>>> A couple 1.13 tagged items still lingering. Going to either
> > kick
> > >>> >> them
> > >>> >>>>>>> out or merge them and get going. Hopefully an RC today or
> > >>> tomorrow.
> > >>> >>>>>>>
> > >>> >>>>>>> Thanks
> > >>> >>>>>>>
> > >>> >>>>>>> On Wed, Jan 20, 2021 at 7:21 AM Mike Thomsen <
> > >>> mikerthomsen@gmail.com
> > >>> >>>
> > >>> >>>>>>> wrote:
> > >>> >>>>>>>
> > >>> >>>>>>>> Bug confirmed. Working on a PR now.
> > >>> >>>>>>>>
> > >>> >>>>>>>> On Wed, Jan 20, 2021 at 8:45 AM Mike Thomsen <
> > >>> >> mikerthomsen@gmail.com
> > >>> >>>>>
> > >>> >>>>>>>> wrote:
> > >>> >>>>>>>>>
> > >>> >>>>>>>>> This morning, I think I found a serious bug in
> > >>> PutCassandraRecord
> > >>> >>>> WRT
> > >>> >>>>>>>>> writing binary data to Cassandra. I'm debugging now. If
> it's
> > >>> >>>> really a
> > >>> >>>>>>>>> bug, I'd appreciate it if we could squeak a fix into 1.13.
> > >>> >>>>>>>>>
> > >>> >>>>>>>>> On Tue, Jan 19, 2021 at 9:54 AM Joe Witt <
> joe.witt@gmail.com
> > >
> > >>> >>>> wrote:
> > >>> >>>>>>>>>>
> > >>> >>>>>>>>>> Team,
> > >>> >>>>>>>>>>
> > >>> >>>>>>>>>> I'm going to initiate RM processes for 1.13. I'll be
> > watching
> > >>> >>>>>>>> closely for
> > >>> >>>>>>>>>> currently tagged 1.13 items to include. If anything is
> > >>> dragging
> > >>> >>>>>>>> I'll just
> > >>> >>>>>>>>>> remove it from 1.13 and we'll pick it up later. Other
> items
> > >>> that
> > >>> >>>>> get
> > >>> >>>>>>>>>> dev/reviewer traction before I cut the RC we can
> include. I
> > >>> will
> > >>> >>>>>>>>>> *probably/hopefully* start that process first thing
> tomorrow
> > >>> >>>>> morning.
> > >>> >>>>>>>>>>
> > >>> >>>>>>>>>>
> > >>> https://issues.apache.org/jira/projects/NIFI/versions/12348700
> > >>> >>>> is
> > >>> >>>>>>>> what i'm
> > >>> >>>>>>>>>> working from.
> > >>> >>>>>>>>>>
> > >>> >>>>>>>>>> Thanks
> > >>> >>>>>>>>>>
> > >>> >>>>>>>>>> On Fri, Jan 15, 2021 at 6:12 PM Waleed Aibany <
> > >>> >>>> walmut44@gmail.com>
> > >>> >>>>>>>> wrote:
> > >>> >>>>>>>>>>
> > >>> >>>>>>>>>>> Hi,
> > >>> >>>>>>>>>>>
> > >>> >>>>>>>>>>> I did rebase to this old PR
> > >>> >>>>>>>> https://github.com/apache/nifi/pull/4167
> > >>> >>>>>>>>>>> Is it possible to include it in 1.13.0
> > >>> >>>>>>>>>>>
> > >>> >>>>>>>>>>> Thank you
> > >>> >>>>>>>>>>>
> > >>> >>>>>>>>>>> On 2021/01/05 15:03:32, Pierre Villard <
> > >>> >>>>>>>> pierre.villard.fr@gmail.com>
> > >>> >>>>>>>>>>> wrote:
> > >>> >>>>>>>>>>>> Hi all,
> > >>> >>>>>>>>>>>>
> > >>> >>>>>>>>>>>> Happy new year to everyone, hope you all had a great
> time.
> > >>> >>>> I'm
> > >>> >>>>>>>> bumping
> > >>> >>>>>>>>>>> this
> > >>> >>>>>>>>>>>> thread up as I think it'd make a lot of sense to release
> > >>> NiFi
> > >>> >>>>>>>> 1.13.0. We
> > >>> >>>>>>>>>>>> have a ton of bug fixes and improvements that would be
> > very
> > >>> >>>>>>>> useful for
> > >>> >>>>>>>>>>> our
> > >>> >>>>>>>>>>>> community.
> > >>> >>>>>>>>>>>>
> > >>> >>>>>>>>>>>> Let's try to see if there are any blockers for a release
> > and
> > >>> >>>>>>>> start the
> > >>> >>>>>>>>>>>> process:
> > >>> >>>>>>>>>>>>
> > >>> >>>>>>>>>>>
> > >>> >>>>>>>>
> > >>> >>>>>
> > >>> >>>>
> > >>> >>
> > >>>
> >
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20NIFI%20AND%20resolution%20%3D%20Unresolved%20AND%20fixVersion%20%3D%201.13.0%20ORDER%20BY%20priority%20DESC%2C%20updated%20DESC
> > >>> >>>>>>>>>>>>
> > >>> >>>>>>>>>>>> Thanks!
> > >>> >>>>>>>>>>>>
> > >>> >>>>>>>>>>>>
> > >>> >>>>>>>>>>>> Le mar. 1 déc. 2020 à 14:49, Bryan Bende <
> > bbende@gmail.com>
> > >>> >>>> a
> > >>> >>>>>>>> écrit :
> > >>> >>>>>>>>>>>>
> > >>> >>>>>>>>>>>>> Chris,
> > >>> >>>>>>>>>>>>>
> > >>> >>>>>>>>>>>>> The illegal reflective access warnings are expected
> when
> > >>> >>>>>>>> running on
> > >>> >>>>>>>>>>> Java
> > >>> >>>>>>>>>>>>> 11.
> > >>> >>>>>>>>>>>>>
> > >>> >>>>>>>>>>>>> The second warning about the provenance repo seems
> like a
> > >>> >>>>>>>> possible
> > >>> >>>>>>>>>>>>> issue due to some recent refactorings made for
> stateless,
> > >>> >>>> we
> > >>> >>>>>>>> should
> > >>> >>>>>>>>>>>>> take a look at that.
> > >>> >>>>>>>>>>>>>
> > >>> >>>>>>>>>>>>> Thanks,
> > >>> >>>>>>>>>>>>>
> > >>> >>>>>>>>>>>>> Bryan
> > >>> >>>>>>>>>>>>>
> > >>> >>>>>>>>>>>>> On Tue, Dec 1, 2020 at 3:58 AM Chris Sampson
> > >>> >>>>>>>>>>>>> <ch...@naimuri.com.invalid> wrote:
> > >>> >>>>>>>>>>>>>>
> > >>> >>>>>>>>>>>>>> Just spotted the following during startup of NiFi
> > >>> >>>>>>>> 1.13.0-SNAPSHOT on
> > >>> >>>>>>>>>>> my
> > >>> >>>>>>>>>>>>>> local machine, which might be worth looking at
> (although
> > >>> >>>>>>>> I've not
> > >>> >>>>>>>>>>> deleted
> > >>> >>>>>>>>>>>>>> and re-created the binaries in a little while, so I
> > could
> > >>> >>>>>>>> have
> > >>> >>>>>>>>>>> something
> > >>> >>>>>>>>>>>>>> wrong in my /lib folder or such):
> > >>> >>>>>>>>>>>>>>
> > >>> >>>>>>>>>>>>>> 2020-12-01 08:52:48,382 ERROR [NiFi logging handler]
> > >>> >>>>>>>>>>>>> org.apache.nifi.StdErr
> > >>> >>>>>>>>>>>>>> WARNING: An illegal reflective access operation has
> > >>> >>>>> occurred
> > >>> >>>>>>>>>>>>>> 2020-12-01 08:52:48,383 ERROR [NiFi logging handler]
> > >>> >>>>>>>>>>>>> org.apache.nifi.StdErr
> > >>> >>>>>>>>>>>>>> WARNING: Illegal reflective access by
> > >>> >>>>>>>>>>>>>> com.sun.xml.bind.v2.runtime.reflect.opt.Injector
> > >>> >>>>>>>>>>>>>>
> > >>> >>>>>>>>
> (file:.../nifi-1.13.0-SNAPSHOT/lib/java11/jaxb-impl-2.3.0.jar)
> > >>> to
> > >>> >>>>>>>>>>> method
> > >>> >>>>>>>>>>>>>>
> > >>> >>>>>>>>
> > >>> java.lang.ClassLoader.defineClass(java.lang.String,byte[],int,int)
> > >>> >>>>>>>>>>>>>> 2020-12-01 08:52:48,383 ERROR [NiFi logging handler]
> > >>> >>>>>>>>>>>>> org.apache.nifi.StdErr
> > >>> >>>>>>>>>>>>>> WARNING: Please consider reporting this to the
> > >>> >>>> maintainers
> > >>> >>>>> of
> > >>> >>>>>>>>>>>>>> com.sun.xml.bind.v2.runtime.reflect.opt.Injector
> > >>> >>>>>>>>>>>>>> 2020-12-01 08:52:48,383 ERROR [NiFi logging handler]
> > >>> >>>>>>>>>>>>> org.apache.nifi.StdErr
> > >>> >>>>>>>>>>>>>> WARNING: Use --illegal-access=warn to enable warnings
> of
> > >>> >>>>>>>> further
> > >>> >>>>>>>>>>> illegal
> > >>> >>>>>>>>>>>>>> reflective access operations
> > >>> >>>>>>>>>>>>>> 2020-12-01 08:52:48,383 ERROR [NiFi logging handler]
> > >>> >>>>>>>>>>>>> org.apache.nifi.StdErr
> > >>> >>>>>>>>>>>>>> WARNING: All illegal access operations will be denied
> in
> > >>> >>>> a
> > >>> >>>>>>>> future
> > >>> >>>>>>>>>>> release
> > >>> >>>>>>>>>>>>>>
> > >>> >>>>>>>>>>>>>> Also:
> > >>> >>>>>>>>>>>>>> 2020-12-01 08:52:52,486 WARN [main]
> > >>> >>>>>>>>>>>>>> o.a.n.n.StandardExtensionDiscoveringManager Failed to
> > >>> >>>>>>>> register
> > >>> >>>>>>>>>>> extension
> > >>> >>>>>>>>>>>>>>
> org.apache.nifi.provenance.VolatileProvenanceRepository
> > >>> >>>> due
> > >>> >>>>>>>> to:
> > >>> >>>>>>>>>>> Attempt
> > >>> >>>>>>>>>>>>> was
> > >>> >>>>>>>>>>>>>> made to load
> > >>> >>>>>>>> org.apache.nifi.provenance.VolatileProvenanceRepository
> > >>> >>>>>>>>>>> from
> > >>> >>>>>>>>>>>>>>
> > >>> >>>>>>>>
> org.apache.nifi:nifi-provenance-repository-nar:1.13.0-SNAPSHOT
> > >>> but
> > >>> >>>>>>>>>>> that
> > >>> >>>>>>>>>>>>>> class name is already loaded/registered from
> > >>> >>>>>>>>>>>>>> org.apache.nifi:nifi-stateless-nar:1.13.0-SNAPSHOT and
> > >>> >>>>>>>> multiple
> > >>> >>>>>>>>>>> versions
> > >>> >>>>>>>>>>>>>> are not supported for this type
> > >>> >>>>>>>>>>>>>>
> > >>> >>>>>>>>>>>>>> These log messages appear just before the NAR
> extraction
> > >>> >>>>>>>> logs during
> > >>> >>>>>>>>>>>>>> instance startup.
> > >>> >>>>>>>>>>>>>>
> > >>> >>>>>>>>>>>>>> Don't know whether these are things that should be
> fixed
> > >>> >>>>>>>> before
> > >>> >>>>>>>>>>> 1.13.0
> > >>> >>>>>>>>>>>>>> and/or have already been looked into, but figured I'd
> > >>> >>>>>>>> mention them so
> > >>> >>>>>>>>>>>>>> they're at least known about.
> > >>> >>>>>>>>>>>>>>
> > >>> >>>>>>>>>>>>>> ---
> > >>> >>>>>>>>>>>>>> *Chris Sampson*
> > >>> >>>>>>>>>>>>>> IT Consultant
> > >>> >>>>>>>>>>>>>> chris.sampson@naimuri.com
> > >>> >>>>>>>>>>>>>> <https://www.naimuri.com/>
> > >>> >>>>>>>>>>>>>>
> > >>> >>>>>>>>>>>>>>
> > >>> >>>>>>>>>>>>>> On Mon, 30 Nov 2020 at 18:50, Nissim Shiman
> > >>> >>>>>>>>>>> <ns...@yahoo.com.invalid>
> > >>> >>>>>>>>>>>>>> wrote:
> > >>> >>>>>>>>>>>>>>
> > >>> >>>>>>>>>>>>>>> Hello Nifi Team,
> > >>> >>>>>>>>>>>>>>>
> > >>> >>>>>>>>>>>>>>> NIFI-7738 [1]
> > >>> >>>> https://github.com/apache/nifi/pull/4563
> > >>> >>>>>>>>>>>>>>> has already been reviewed/tested by a fellow
> > >>> >>>> contributer
> > >>> >>>>>>>>>>>>>>> I would greatly appreciate a committer moving this to
> > >>> >>>>> main
> > >>> >>>>>>>> for
> > >>> >>>>>>>>>>> 1.13.0
> > >>> >>>>>>>>>>>>>>> Thanks,
> > >>> >>>>>>>>>>>>>>> Nissim Shiman
> > >>> >>>>>>>>>>>>>>>
> > >>> >>>>>>>>>>>>>>> [1] https://issues.apache.org/jira/browse/NIFI-7738
> > >>> >>>>>>>>>>>>>>> On Sunday, November 29, 2020, 07:12:12 PM EST, Matt
> > >>> >>>>>>>> Burgess <
> > >>> >>>>>>>>>>>>>>> mattyb149@apache.org> wrote:
> > >>> >>>>>>>>>>>>>>>
> > >>> >>>>>>>>>>>>>>> I just merged Mike's Cassandra DMC PR, reviewing the
> > >>> >>>>>>>> graph stuff
> > >>> >>>>>>>>>>> now.
> > >>> >>>>>>>>>>>>>>>
> > >>> >>>>>>>>>>>>>>> I have a bunch of open PRs [1], I don't think any are
> > >>> >>>>>>>> blockers for
> > >>> >>>>>>>>>>>>>>> 1.13.0 but thought I'd take this opportunity to find
> > >>> >>>> some
> > >>> >>>>>>>>>>> reviewers :)
> > >>> >>>>>>>>>>>>>>>
> > >>> >>>>>>>>>>>>>>> Regards,
> > >>> >>>>>>>>>>>>>>> Matt
> > >>> >>>>>>>>>>>>>>>
> > >>> >>>>>>>>>>>>>>> [1] https://github.com/apache/nifi/pulls/mattyb149
> > >>> >>>>>>>>>>>>>>>
> > >>> >>>>>>>>>>>>>>> On Sat, Nov 28, 2020 at 10:13 AM Phillip Grenier
> > >>> >>>>>>>>>>> <ph...@nifi.rocks>
> > >>> >>>>>>>>>>>>>>> wrote:
> > >>> >>>>>>>>>>>>>>>>
> > >>> >>>>>>>>>>>>>>>> I wouldn't mind
> > >>> >>>>> https://github.com/apache/nifi/pull/4554
> > >>> >>>>>>>> making
> > >>> >>>>>>>>>>> it
> > >>> >>>>>>>>>>>>> in.
> > >>> >>>>>>>>>>>>>>> Have
> > >>> >>>>>>>>>>>>>>>> seen a couple more instances where people have
> > >>> >>>> created
> > >>> >>>>>>>> custom
> > >>> >>>>>>>>>>>>> processors
> > >>> >>>>>>>>>>>>>>> to
> > >>> >>>>>>>>>>>>>>>> work around this PR.
> > >>> >>>>>>>>>>>>>>>>
> > >>> >>>>>>>>>>>>>>>> On Thu, Nov 26, 2020 at 11:10 AM Mike Thomsen <
> > >>> >>>>>>>>>>>>> mikerthomsen@gmail.com>
> > >>> >>>>>>>>>>>>>>>> wrote:
> > >>> >>>>>>>>>>>>>>>>
> > >>> >>>>>>>>>>>>>>>>> Also, for most of us (committers and community
> > >>> >>>>>>>> members), it's a
> > >>> >>>>>>>>>>>>>>>>> holiday season so might be good to delay a release
> > >>> >>>> to
> > >>> >>>>>>>> early
> > >>> >>>>>>>>>>> January
> > >>> >>>>>>>>>>>>>>>>> anyway. Just a thought.
> > >>> >>>>>>>>>>>>>>>>>
> > >>> >>>>>>>>>>>>>>>>> On Thu, Nov 26, 2020 at 11:08 AM Mike Thomsen <
> > >>> >>>>>>>>>>>>> mikerthomsen@gmail.com>
> > >>> >>>>>>>>>>>>>>>>> wrote:
> > >>> >>>>>>>>>>>>>>>>>>
> > >>> >>>>>>>>>>>>>>>>>> https://github.com/apache/nifi/pull/4638 - This
> > >>> >>>> is
> > >>> >>>>>>>> a big
> > >>> >>>>>>>>>>>>> increase in
> > >>> >>>>>>>>>>>>>>>>>> graph functionality, and I want to give him a
> > >>> >>>>> chance
> > >>> >>>>>>>> to get
> > >>> >>>>>>>>>>> his
> > >>> >>>>>>>>>>>>> first
> > >>> >>>>>>>>>>>>>>>>>> contribution in with 1.13 (we may have some more
> > >>> >>>> of
> > >>> >>>>>>>> his work
> > >>> >>>>>>>>>>> we
> > >>> >>>>>>>>>>>>> can
> > >>> >>>>>>>>>>>>>>>>>> open source).
> > >>> >>>>>>>>>>>>>>>>>>
> > >>> >>>>>>>>>>>>>>>>>> Matt's also reviewing some of my Cassandra and
> > >>> >>>>> graph
> > >>> >>>>>>>> tickets
> > >>> >>>>>>>>>>> as
> > >>> >>>>>>>>>>>>> well.
> > >>> >>>>>>>>>>>>>>>>>> I wouldn't call those **blockers**, but having
> > >>> >>>> the
> > >>> >>>>>>>> Cassandra
> > >>> >>>>>>>>>>> DMC
> > >>> >>>>>>>>>>>>>>> fully
> > >>> >>>>>>>>>>>>>>>>>> fleshed out would be nice.
> > >>> >>>>>>>>>>>>>>>>>>
> > >>> >>>>>>>>>>>>>>>>>> On Thu, Nov 26, 2020 at 9:10 AM Otto Fowler <
> > >>> >>>>>>>>>>>>> ottobackwards@gmail.com
> > >>> >>>>>>>>>>>>>>>>
> > >>> >>>>>>>>>>>>>>>>> wrote:
> > >>> >>>>>>>>>>>>>>>>>>>
> > >>> >>>>>>>>>>>>>>>>>>> NIFI-7795
> > >>> >>>>>>>> https://github.com/apache/nifi/pull/4656
> > >>> >>>>>>>>>>>>>>>>>>> NIFI-7761
> > >>> >>>>> https://github.com/apache/nifi/pull/4513
> > >>> >>>>>>>>>>>>>>>>>>> NIFI-2072
> > >>> >>>>> https://github.com/apache/nifi/pull/4384
> > >>> >>>>>>>>>>>>>>>>>>>
> > >>> >>>>>>>>>>>>>>>>>>> From: Pierre Villard <
> > >>> >>>>> pierre.villard.fr@gmail.com>
> > >>> >>>>>>>>>>>>>>>>>>> <pi...@gmail.com>
> > >>> >>>>>>>>>>>>>>>>>>> Reply: dev@nifi.apache.org <
> > >>> >>>> dev@nifi.apache.org>
> > >>> >>>>> <
> > >>> >>>>>>>>>>>>>>> dev@nifi.apache.org>
> > >>> >>>>>>>>>>>>>>>>>>> Date: November 26, 2020 at 04:55:56
> > >>> >>>>>>>>>>>>>>>>>>> To: dev@nifi.apache.org <de...@nifi.apache.org>
> > >>> >>>> <
> > >>> >>>>>>>>>>>>> dev@nifi.apache.org
> > >>> >>>>>>>>>>>>>>>>
> > >>> >>>>>>>>>>>>>>>>>>> Subject: [DISCUSS] Release of Apache NiFi
> > >>> >>>> 1.13.0
> > >>> >>>>>>>>>>>>>>>>>>>
> > >>> >>>>>>>>>>>>>>>>>>> Hi community,
> > >>> >>>>>>>>>>>>>>>>>>>
> > >>> >>>>>>>>>>>>>>>>>>> Starting a discussion thread around the release
> > >>> >>>>> of
> > >>> >>>>>>>> NiFi
> > >>> >>>>>>>>>>>>> 1.13.0. We
> > >>> >>>>>>>>>>>>>>>>> added
> > >>> >>>>>>>>>>>>>>>>>>> quite a lot of significant improvements and
> > >>> >>>>>>>> features since
> > >>> >>>>>>>>>>> the
> > >>> >>>>>>>>>>>>>>> release
> > >>> >>>>>>>>>>>>>>>>> of
> > >>> >>>>>>>>>>>>>>>>>>> 1.12.1 - I see 143 JIRAs with 1.13.0 as the fix
> > >>> >>>>>>>> version. I
> > >>> >>>>>>>>>>>>> think it
> > >>> >>>>>>>>>>>>>>>>> makes
> > >>> >>>>>>>>>>>>>>>>>>> sense to consider a new release.
> > >>> >>>>>>>>>>>>>>>>>>>
> > >>> >>>>>>>>>>>>>>>>>>> Please share here the JIRAs with opened pull
> > >>> >>>>>>>> requests that
> > >>> >>>>>>>>>>> we
> > >>> >>>>>>>>>>>>> would
> > >>> >>>>>>>>>>>>>>>>> need to
> > >>> >>>>>>>>>>>>>>>>>>> look at to make this release happen.
> > >>> >>>>>>>>>>>>>>>>>>>
> > >>> >>>>>>>>>>>>>>>>>>> Thanks,
> > >>> >>>>>>>>>>>>>>>>>>> Pierre
> > >>> >>>>>>>>>>>>>>>>>
> > >>> >>>>>>>>>>>>>>>
> > >>> >>>>>>>>>>>>>
> > >>> >>>>>>>>>>>>
> > >>> >>>>>>>>>>>
> > >>> >>>>>>>>
> > >>> >>>>>>>
> > >>> >>>>>
> > >>> >>>>
> > >>> >>
> > >>> >>
> > >>>
> > >>>
> >
>
Re: [DISCUSS] Release of Apache NiFi 1.13.0
Posted by Mark Bean <ma...@gmail.com>.
Today, I also noticed that the following modules still have code in them.
However, they are not listed as a module in the corresponding pom.xml.
nifi-docker/docker-compose
nifi-docker/dockermaven-stateless
nifi-framework-bundle/nifi-framework/nifi-stateless
Is this dead code that should simply be removed? Also, I did not email this
out yet because I did not finish searching the codebase for other such
"unused" code.
At a minimum, as best I can tell, the above can be removed entirely.
-Mark
On Mon, Feb 1, 2021 at 4:33 PM Joe Witt <jo...@gmail.com> wrote:
> Team
>
> starting RC2. Joey Frazee noted "I noticed that
> nifi-docker/dockermaven-stateless/pom.xml
> and nifi-docker/docker-compose/docker-compose.yml in the source package and
> tag are still using 1.13.0-SNAPSHOT" while looking at RC1. I have no
> instructions/guidance on what to do with those as an RM and I've never
> modified them before. If we're going to keep these in the build, and I
> would advocate actually that we remove them, then someone needs to
> determine the whole lifecycle of how to manage/maintain them and
> document the steps for a RelMgr. The dockerhub module we do have guidance
> for and they're currently correct.
>
> Thanks
>
> On Mon, Feb 1, 2021 at 10:14 AM Joe Witt <jo...@gmail.com> wrote:
>
> > Team,
> >
> > Will put RC2 for 1.13 back up today hopefully. The fix is in for the
> > issue that sank the release.
> >
> > Thanks
> > Joe
> >
> > On Thu, Jan 28, 2021 at 8:18 AM Joe Witt <jo...@gmail.com> wrote:
> >
> >> Otto
> >>
> >> Truth is we dont know. We cannot readily test with the amazing matrix
> >> that exists. So we are leaning toward ensuring recent versions work as
> >> expected.
> >>
> >> The goal is java 8 and 11 broadly right now. But these internal changes
> >> of exception types being used are brutal.
> >>
> >> Thanks
> >>
> >> On Thu, Jan 28, 2021 at 8:15 AM Otto Fowler <ot...@gmail.com>
> >> wrote:
> >>
> >>> Thanks Joe,
> >>>
> >>> I’m started down that road right after I sent this. I’ll update when I
> >>> know.
> >>> I _have_ been building nifi with this jdk all along though.
> >>>
> >>> If there are jdk minimum requirements, should they be documented ( or
> >>> are they and I missed it)?
> >>>
> >>> > On Jan 28, 2021, at 09:35, Joe Witt <jo...@gmail.com> wrote:
> >>> >
> >>> > Otto
> >>> >
> >>> > I dont know we can keep all variants of Java 8 happy. That one is
> >>> nearly
> >>> > three years old. I would say try with something more recent. It has
> >>> been
> >>> > pretty shocking how many api changes we have seen across these
> builds.
> >>> >
> >>> > Thanks
> >>> >
> >>> > On Thu, Jan 28, 2021 at 6:12 AM Otto Fowler <ottobackwards@gmail.com
> >
> >>> wrote:
> >>> >
> >>> >> I’m trying to validate RC-1 and I’m seeing this exception building /
> >>> >> running tests
> >>> >>
> >>> >> [INFO] Running org.apache.nifi.processors.standard.TestListenTCP
> >>> >> [ERROR] Tests run: 6, Failures: 1, Errors: 0, Skipped: 0, Time
> >>> elapsed:
> >>> >> 4.499 s <<< FAILURE! - in
> >>> org.apache.nifi.processors.standard.TestListenTCP
> >>> >> [ERROR]
> >>> >>
> >>>
> testTLSClientAuthRequiredAndClientCertNotProvided(org.apache.nifi.processors.standard.TestListenTCP)
> >>> >> Time elapsed: 0.127 s <<< FAILURE!
> >>> >> java.lang.AssertionError: unexpected exception type thrown;
> >>> >> expected:<javax.net.ssl.SSLException> but
> >>> was:<java.net.SocketException>
> >>> >> at
> >>> >>
> >>>
> org.apache.nifi.processors.standard.TestListenTCP.testTLSClientAuthRequiredAndClientCertNotProvided(TestListenTCP.java:159)
> >>> >> Caused by: java.net.SocketException: Connection reset
> >>> >> at
> >>> >>
> >>>
> org.apache.nifi.processors.standard.TestListenTCP.runTCP(TestListenTCP.java:209)
> >>> >> at
> >>> >>
> >>>
> org.apache.nifi.processors.standard.TestListenTCP.lambda$testTLSClientAuthRequiredAndClientCertNotProvided$0(TestListenTCP.java:160)
> >>> >> at
> >>> >>
> >>>
> org.apache.nifi.processors.standard.TestListenTCP.testTLSClientAuthRequiredAndClientCertNotProvided(TestListenTCP.java:159)
> >>> >>
> >>> >>
> >>> >>
> >>> >> Apache Maven 3.6.3 (cecedd343002696d0abb50b32b541b8a6ba2883f)
> >>> >> Maven home: /usr/local/Cellar/maven/3.6.3_1/libexec
> >>> >> Java version: 1.8.0_171, vendor: Oracle Corporation, runtime:
> >>> >> /Library/Java/JavaVirtualMachines/jdk1.8.0_171.jdk/Contents/Home/jre
> >>> >> Default locale: en_US, platform encoding: UTF-8
> >>> >> OS name: "mac os x", version: "10.16", arch: "x86_64", family: “mac"
> >>> >>
> >>> >>
> >>> >>
> >>> >>> On Jan 27, 2021, at 10:31, Joe Witt <jo...@gmail.com> wrote:
> >>> >>>
> >>> >>> ...in this brutal game of wach a mole another couple brittle tests
> >>> have
> >>> >>> emerged on the Java 11 line.
> >>> >>> https://issues.apache.org/jira/browse/NIFI-8177 will get that
> looked
> >>> >> into.
> >>> >>> And I'm also seeing if for some reason adding a bit more
> >>> horsepower/cpu
> >>> >>> usage to the github tests will help. Things had been very stable
> for
> >>> >> quite
> >>> >>> a while until the update to the latest 11.0.10 azul jdk came out so
> >>> kind
> >>> >> of
> >>> >>> strange the tests became less reliable then. Anyway dont want to
> >>> initiate
> >>> >>> the RC until things seem stable otherwise it makes the vote process
> >>> more
> >>> >>> difficult and further when the builds dont pass it makes the
> already
> >>> >>> difficult task of staying apace with PRs more inivolved.
> >>> >>>
> >>> >>> Thanks
> >>> >>>
> >>> >>> On Wed, Jan 27, 2021 at 12:19 AM Pierre Villard <
> >>> >> pierre.villard.fr@gmail.com>
> >>> >>> wrote:
> >>> >>>
> >>> >>>> Awesome, thanks Joe!
> >>> >>>>
> >>> >>>> Le mer. 27 janv. 2021 à 10:16, Joe Witt <jo...@gmail.com> a
> >>> écrit :
> >>> >>>>
> >>> >>>>> Team,
> >>> >>>>>
> >>> >>>>> Ok wow so the issue with build failures that emerged has been
> >>> resolved
> >>> >> it
> >>> >>>>> appears thanks to a lot of effort by exceptionfactory. The other
> >>> >>>> lingering
> >>> >>>>> commits/PRs are in and I think most of what folks asked for in
> this
> >>> >>>>> thread. I just put in a commit which drops a few older/less
> common
> >>> >> nars
> >>> >>>>> from convenience binary inclusion to get us back under the
> maximum
> >>> size
> >>> >>>>> again. And now I think we can initiate RC1 build for 1.13.0.
> >>> >>>>>
> >>> >>>>> That should be published in the AM.
> >>> >>>>>
> >>> >>>>> Thanks
> >>> >>>>>
> >>> >>>>> On Mon, Jan 25, 2021 at 6:40 AM Joe Witt <jo...@gmail.com>
> >>> wrote:
> >>> >>>>>
> >>> >>>>>> Team,
> >>> >>>>>>
> >>> >>>>>> There is a TZ handling issue
> >>> >>>>>> https://issues.apache.org/jira/browse/NIFI-8023 that needs a
> >>> >>>> resolution
> >>> >>>>>> and there is also a new issue that has emerged on Github
> >>> Actions/CI
> >>> >>>>>> https://github.com/apache/nifi/actions which is resulting in
> >>> broken
> >>> >>>>>> builds. This emerged in the latest Java 11 Azul release and in
> >>> Github
> >>> >>>>> CI.
> >>> >>>>>> I've tried to replicate with no success on a local linux machine
> >>> with
> >>> >>>> the
> >>> >>>>>> exact same JVM/version.
> >>> >>>>>>
> >>> >>>>>> Once these are wrapped I'll initiate the RC. Great work to all
> >>> >>>> involved
> >>> >>>>>> in helping get the release candidate this close.
> >>> >>>>>>
> >>> >>>>>> Thanks
> >>> >>>>>> Joe
> >>> >>>>>>
> >>> >>>>>> On Thu, Jan 21, 2021 at 8:30 AM Joe Witt <jo...@gmail.com>
> >>> wrote:
> >>> >>>>>>
> >>> >>>>>>> Team,
> >>> >>>>>>>
> >>> >>>>>>> A couple 1.13 tagged items still lingering. Going to either
> kick
> >>> >> them
> >>> >>>>>>> out or merge them and get going. Hopefully an RC today or
> >>> tomorrow.
> >>> >>>>>>>
> >>> >>>>>>> Thanks
> >>> >>>>>>>
> >>> >>>>>>> On Wed, Jan 20, 2021 at 7:21 AM Mike Thomsen <
> >>> mikerthomsen@gmail.com
> >>> >>>
> >>> >>>>>>> wrote:
> >>> >>>>>>>
> >>> >>>>>>>> Bug confirmed. Working on a PR now.
> >>> >>>>>>>>
> >>> >>>>>>>> On Wed, Jan 20, 2021 at 8:45 AM Mike Thomsen <
> >>> >> mikerthomsen@gmail.com
> >>> >>>>>
> >>> >>>>>>>> wrote:
> >>> >>>>>>>>>
> >>> >>>>>>>>> This morning, I think I found a serious bug in
> >>> PutCassandraRecord
> >>> >>>> WRT
> >>> >>>>>>>>> writing binary data to Cassandra. I'm debugging now. If it's
> >>> >>>> really a
> >>> >>>>>>>>> bug, I'd appreciate it if we could squeak a fix into 1.13.
> >>> >>>>>>>>>
> >>> >>>>>>>>> On Tue, Jan 19, 2021 at 9:54 AM Joe Witt <joe.witt@gmail.com
> >
> >>> >>>> wrote:
> >>> >>>>>>>>>>
> >>> >>>>>>>>>> Team,
> >>> >>>>>>>>>>
> >>> >>>>>>>>>> I'm going to initiate RM processes for 1.13. I'll be
> watching
> >>> >>>>>>>> closely for
> >>> >>>>>>>>>> currently tagged 1.13 items to include. If anything is
> >>> dragging
> >>> >>>>>>>> I'll just
> >>> >>>>>>>>>> remove it from 1.13 and we'll pick it up later. Other items
> >>> that
> >>> >>>>> get
> >>> >>>>>>>>>> dev/reviewer traction before I cut the RC we can include. I
> >>> will
> >>> >>>>>>>>>> *probably/hopefully* start that process first thing tomorrow
> >>> >>>>> morning.
> >>> >>>>>>>>>>
> >>> >>>>>>>>>>
> >>> https://issues.apache.org/jira/projects/NIFI/versions/12348700
> >>> >>>> is
> >>> >>>>>>>> what i'm
> >>> >>>>>>>>>> working from.
> >>> >>>>>>>>>>
> >>> >>>>>>>>>> Thanks
> >>> >>>>>>>>>>
> >>> >>>>>>>>>> On Fri, Jan 15, 2021 at 6:12 PM Waleed Aibany <
> >>> >>>> walmut44@gmail.com>
> >>> >>>>>>>> wrote:
> >>> >>>>>>>>>>
> >>> >>>>>>>>>>> Hi,
> >>> >>>>>>>>>>>
> >>> >>>>>>>>>>> I did rebase to this old PR
> >>> >>>>>>>> https://github.com/apache/nifi/pull/4167
> >>> >>>>>>>>>>> Is it possible to include it in 1.13.0
> >>> >>>>>>>>>>>
> >>> >>>>>>>>>>> Thank you
> >>> >>>>>>>>>>>
> >>> >>>>>>>>>>> On 2021/01/05 15:03:32, Pierre Villard <
> >>> >>>>>>>> pierre.villard.fr@gmail.com>
> >>> >>>>>>>>>>> wrote:
> >>> >>>>>>>>>>>> Hi all,
> >>> >>>>>>>>>>>>
> >>> >>>>>>>>>>>> Happy new year to everyone, hope you all had a great time.
> >>> >>>> I'm
> >>> >>>>>>>> bumping
> >>> >>>>>>>>>>> this
> >>> >>>>>>>>>>>> thread up as I think it'd make a lot of sense to release
> >>> NiFi
> >>> >>>>>>>> 1.13.0. We
> >>> >>>>>>>>>>>> have a ton of bug fixes and improvements that would be
> very
> >>> >>>>>>>> useful for
> >>> >>>>>>>>>>> our
> >>> >>>>>>>>>>>> community.
> >>> >>>>>>>>>>>>
> >>> >>>>>>>>>>>> Let's try to see if there are any blockers for a release
> and
> >>> >>>>>>>> start the
> >>> >>>>>>>>>>>> process:
> >>> >>>>>>>>>>>>
> >>> >>>>>>>>>>>
> >>> >>>>>>>>
> >>> >>>>>
> >>> >>>>
> >>> >>
> >>>
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20NIFI%20AND%20resolution%20%3D%20Unresolved%20AND%20fixVersion%20%3D%201.13.0%20ORDER%20BY%20priority%20DESC%2C%20updated%20DESC
> >>> >>>>>>>>>>>>
> >>> >>>>>>>>>>>> Thanks!
> >>> >>>>>>>>>>>>
> >>> >>>>>>>>>>>>
> >>> >>>>>>>>>>>> Le mar. 1 déc. 2020 à 14:49, Bryan Bende <
> bbende@gmail.com>
> >>> >>>> a
> >>> >>>>>>>> écrit :
> >>> >>>>>>>>>>>>
> >>> >>>>>>>>>>>>> Chris,
> >>> >>>>>>>>>>>>>
> >>> >>>>>>>>>>>>> The illegal reflective access warnings are expected when
> >>> >>>>>>>> running on
> >>> >>>>>>>>>>> Java
> >>> >>>>>>>>>>>>> 11.
> >>> >>>>>>>>>>>>>
> >>> >>>>>>>>>>>>> The second warning about the provenance repo seems like a
> >>> >>>>>>>> possible
> >>> >>>>>>>>>>>>> issue due to some recent refactorings made for stateless,
> >>> >>>> we
> >>> >>>>>>>> should
> >>> >>>>>>>>>>>>> take a look at that.
> >>> >>>>>>>>>>>>>
> >>> >>>>>>>>>>>>> Thanks,
> >>> >>>>>>>>>>>>>
> >>> >>>>>>>>>>>>> Bryan
> >>> >>>>>>>>>>>>>
> >>> >>>>>>>>>>>>> On Tue, Dec 1, 2020 at 3:58 AM Chris Sampson
> >>> >>>>>>>>>>>>> <ch...@naimuri.com.invalid> wrote:
> >>> >>>>>>>>>>>>>>
> >>> >>>>>>>>>>>>>> Just spotted the following during startup of NiFi
> >>> >>>>>>>> 1.13.0-SNAPSHOT on
> >>> >>>>>>>>>>> my
> >>> >>>>>>>>>>>>>> local machine, which might be worth looking at (although
> >>> >>>>>>>> I've not
> >>> >>>>>>>>>>> deleted
> >>> >>>>>>>>>>>>>> and re-created the binaries in a little while, so I
> could
> >>> >>>>>>>> have
> >>> >>>>>>>>>>> something
> >>> >>>>>>>>>>>>>> wrong in my /lib folder or such):
> >>> >>>>>>>>>>>>>>
> >>> >>>>>>>>>>>>>> 2020-12-01 08:52:48,382 ERROR [NiFi logging handler]
> >>> >>>>>>>>>>>>> org.apache.nifi.StdErr
> >>> >>>>>>>>>>>>>> WARNING: An illegal reflective access operation has
> >>> >>>>> occurred
> >>> >>>>>>>>>>>>>> 2020-12-01 08:52:48,383 ERROR [NiFi logging handler]
> >>> >>>>>>>>>>>>> org.apache.nifi.StdErr
> >>> >>>>>>>>>>>>>> WARNING: Illegal reflective access by
> >>> >>>>>>>>>>>>>> com.sun.xml.bind.v2.runtime.reflect.opt.Injector
> >>> >>>>>>>>>>>>>>
> >>> >>>>>>>> (file:.../nifi-1.13.0-SNAPSHOT/lib/java11/jaxb-impl-2.3.0.jar)
> >>> to
> >>> >>>>>>>>>>> method
> >>> >>>>>>>>>>>>>>
> >>> >>>>>>>>
> >>> java.lang.ClassLoader.defineClass(java.lang.String,byte[],int,int)
> >>> >>>>>>>>>>>>>> 2020-12-01 08:52:48,383 ERROR [NiFi logging handler]
> >>> >>>>>>>>>>>>> org.apache.nifi.StdErr
> >>> >>>>>>>>>>>>>> WARNING: Please consider reporting this to the
> >>> >>>> maintainers
> >>> >>>>> of
> >>> >>>>>>>>>>>>>> com.sun.xml.bind.v2.runtime.reflect.opt.Injector
> >>> >>>>>>>>>>>>>> 2020-12-01 08:52:48,383 ERROR [NiFi logging handler]
> >>> >>>>>>>>>>>>> org.apache.nifi.StdErr
> >>> >>>>>>>>>>>>>> WARNING: Use --illegal-access=warn to enable warnings of
> >>> >>>>>>>> further
> >>> >>>>>>>>>>> illegal
> >>> >>>>>>>>>>>>>> reflective access operations
> >>> >>>>>>>>>>>>>> 2020-12-01 08:52:48,383 ERROR [NiFi logging handler]
> >>> >>>>>>>>>>>>> org.apache.nifi.StdErr
> >>> >>>>>>>>>>>>>> WARNING: All illegal access operations will be denied in
> >>> >>>> a
> >>> >>>>>>>> future
> >>> >>>>>>>>>>> release
> >>> >>>>>>>>>>>>>>
> >>> >>>>>>>>>>>>>> Also:
> >>> >>>>>>>>>>>>>> 2020-12-01 08:52:52,486 WARN [main]
> >>> >>>>>>>>>>>>>> o.a.n.n.StandardExtensionDiscoveringManager Failed to
> >>> >>>>>>>> register
> >>> >>>>>>>>>>> extension
> >>> >>>>>>>>>>>>>> org.apache.nifi.provenance.VolatileProvenanceRepository
> >>> >>>> due
> >>> >>>>>>>> to:
> >>> >>>>>>>>>>> Attempt
> >>> >>>>>>>>>>>>> was
> >>> >>>>>>>>>>>>>> made to load
> >>> >>>>>>>> org.apache.nifi.provenance.VolatileProvenanceRepository
> >>> >>>>>>>>>>> from
> >>> >>>>>>>>>>>>>>
> >>> >>>>>>>> org.apache.nifi:nifi-provenance-repository-nar:1.13.0-SNAPSHOT
> >>> but
> >>> >>>>>>>>>>> that
> >>> >>>>>>>>>>>>>> class name is already loaded/registered from
> >>> >>>>>>>>>>>>>> org.apache.nifi:nifi-stateless-nar:1.13.0-SNAPSHOT and
> >>> >>>>>>>> multiple
> >>> >>>>>>>>>>> versions
> >>> >>>>>>>>>>>>>> are not supported for this type
> >>> >>>>>>>>>>>>>>
> >>> >>>>>>>>>>>>>> These log messages appear just before the NAR extraction
> >>> >>>>>>>> logs during
> >>> >>>>>>>>>>>>>> instance startup.
> >>> >>>>>>>>>>>>>>
> >>> >>>>>>>>>>>>>> Don't know whether these are things that should be fixed
> >>> >>>>>>>> before
> >>> >>>>>>>>>>> 1.13.0
> >>> >>>>>>>>>>>>>> and/or have already been looked into, but figured I'd
> >>> >>>>>>>> mention them so
> >>> >>>>>>>>>>>>>> they're at least known about.
> >>> >>>>>>>>>>>>>>
> >>> >>>>>>>>>>>>>> ---
> >>> >>>>>>>>>>>>>> *Chris Sampson*
> >>> >>>>>>>>>>>>>> IT Consultant
> >>> >>>>>>>>>>>>>> chris.sampson@naimuri.com
> >>> >>>>>>>>>>>>>> <https://www.naimuri.com/>
> >>> >>>>>>>>>>>>>>
> >>> >>>>>>>>>>>>>>
> >>> >>>>>>>>>>>>>> On Mon, 30 Nov 2020 at 18:50, Nissim Shiman
> >>> >>>>>>>>>>> <ns...@yahoo.com.invalid>
> >>> >>>>>>>>>>>>>> wrote:
> >>> >>>>>>>>>>>>>>
> >>> >>>>>>>>>>>>>>> Hello Nifi Team,
> >>> >>>>>>>>>>>>>>>
> >>> >>>>>>>>>>>>>>> NIFI-7738 [1]
> >>> >>>> https://github.com/apache/nifi/pull/4563
> >>> >>>>>>>>>>>>>>> has already been reviewed/tested by a fellow
> >>> >>>> contributer
> >>> >>>>>>>>>>>>>>> I would greatly appreciate a committer moving this to
> >>> >>>>> main
> >>> >>>>>>>> for
> >>> >>>>>>>>>>> 1.13.0
> >>> >>>>>>>>>>>>>>> Thanks,
> >>> >>>>>>>>>>>>>>> Nissim Shiman
> >>> >>>>>>>>>>>>>>>
> >>> >>>>>>>>>>>>>>> [1] https://issues.apache.org/jira/browse/NIFI-7738
> >>> >>>>>>>>>>>>>>> On Sunday, November 29, 2020, 07:12:12 PM EST, Matt
> >>> >>>>>>>> Burgess <
> >>> >>>>>>>>>>>>>>> mattyb149@apache.org> wrote:
> >>> >>>>>>>>>>>>>>>
> >>> >>>>>>>>>>>>>>> I just merged Mike's Cassandra DMC PR, reviewing the
> >>> >>>>>>>> graph stuff
> >>> >>>>>>>>>>> now.
> >>> >>>>>>>>>>>>>>>
> >>> >>>>>>>>>>>>>>> I have a bunch of open PRs [1], I don't think any are
> >>> >>>>>>>> blockers for
> >>> >>>>>>>>>>>>>>> 1.13.0 but thought I'd take this opportunity to find
> >>> >>>> some
> >>> >>>>>>>>>>> reviewers :)
> >>> >>>>>>>>>>>>>>>
> >>> >>>>>>>>>>>>>>> Regards,
> >>> >>>>>>>>>>>>>>> Matt
> >>> >>>>>>>>>>>>>>>
> >>> >>>>>>>>>>>>>>> [1] https://github.com/apache/nifi/pulls/mattyb149
> >>> >>>>>>>>>>>>>>>
> >>> >>>>>>>>>>>>>>> On Sat, Nov 28, 2020 at 10:13 AM Phillip Grenier
> >>> >>>>>>>>>>> <ph...@nifi.rocks>
> >>> >>>>>>>>>>>>>>> wrote:
> >>> >>>>>>>>>>>>>>>>
> >>> >>>>>>>>>>>>>>>> I wouldn't mind
> >>> >>>>> https://github.com/apache/nifi/pull/4554
> >>> >>>>>>>> making
> >>> >>>>>>>>>>> it
> >>> >>>>>>>>>>>>> in.
> >>> >>>>>>>>>>>>>>> Have
> >>> >>>>>>>>>>>>>>>> seen a couple more instances where people have
> >>> >>>> created
> >>> >>>>>>>> custom
> >>> >>>>>>>>>>>>> processors
> >>> >>>>>>>>>>>>>>> to
> >>> >>>>>>>>>>>>>>>> work around this PR.
> >>> >>>>>>>>>>>>>>>>
> >>> >>>>>>>>>>>>>>>> On Thu, Nov 26, 2020 at 11:10 AM Mike Thomsen <
> >>> >>>>>>>>>>>>> mikerthomsen@gmail.com>
> >>> >>>>>>>>>>>>>>>> wrote:
> >>> >>>>>>>>>>>>>>>>
> >>> >>>>>>>>>>>>>>>>> Also, for most of us (committers and community
> >>> >>>>>>>> members), it's a
> >>> >>>>>>>>>>>>>>>>> holiday season so might be good to delay a release
> >>> >>>> to
> >>> >>>>>>>> early
> >>> >>>>>>>>>>> January
> >>> >>>>>>>>>>>>>>>>> anyway. Just a thought.
> >>> >>>>>>>>>>>>>>>>>
> >>> >>>>>>>>>>>>>>>>> On Thu, Nov 26, 2020 at 11:08 AM Mike Thomsen <
> >>> >>>>>>>>>>>>> mikerthomsen@gmail.com>
> >>> >>>>>>>>>>>>>>>>> wrote:
> >>> >>>>>>>>>>>>>>>>>>
> >>> >>>>>>>>>>>>>>>>>> https://github.com/apache/nifi/pull/4638 - This
> >>> >>>> is
> >>> >>>>>>>> a big
> >>> >>>>>>>>>>>>> increase in
> >>> >>>>>>>>>>>>>>>>>> graph functionality, and I want to give him a
> >>> >>>>> chance
> >>> >>>>>>>> to get
> >>> >>>>>>>>>>> his
> >>> >>>>>>>>>>>>> first
> >>> >>>>>>>>>>>>>>>>>> contribution in with 1.13 (we may have some more
> >>> >>>> of
> >>> >>>>>>>> his work
> >>> >>>>>>>>>>> we
> >>> >>>>>>>>>>>>> can
> >>> >>>>>>>>>>>>>>>>>> open source).
> >>> >>>>>>>>>>>>>>>>>>
> >>> >>>>>>>>>>>>>>>>>> Matt's also reviewing some of my Cassandra and
> >>> >>>>> graph
> >>> >>>>>>>> tickets
> >>> >>>>>>>>>>> as
> >>> >>>>>>>>>>>>> well.
> >>> >>>>>>>>>>>>>>>>>> I wouldn't call those **blockers**, but having
> >>> >>>> the
> >>> >>>>>>>> Cassandra
> >>> >>>>>>>>>>> DMC
> >>> >>>>>>>>>>>>>>> fully
> >>> >>>>>>>>>>>>>>>>>> fleshed out would be nice.
> >>> >>>>>>>>>>>>>>>>>>
> >>> >>>>>>>>>>>>>>>>>> On Thu, Nov 26, 2020 at 9:10 AM Otto Fowler <
> >>> >>>>>>>>>>>>> ottobackwards@gmail.com
> >>> >>>>>>>>>>>>>>>>
> >>> >>>>>>>>>>>>>>>>> wrote:
> >>> >>>>>>>>>>>>>>>>>>>
> >>> >>>>>>>>>>>>>>>>>>> NIFI-7795
> >>> >>>>>>>> https://github.com/apache/nifi/pull/4656
> >>> >>>>>>>>>>>>>>>>>>> NIFI-7761
> >>> >>>>> https://github.com/apache/nifi/pull/4513
> >>> >>>>>>>>>>>>>>>>>>> NIFI-2072
> >>> >>>>> https://github.com/apache/nifi/pull/4384
> >>> >>>>>>>>>>>>>>>>>>>
> >>> >>>>>>>>>>>>>>>>>>> From: Pierre Villard <
> >>> >>>>> pierre.villard.fr@gmail.com>
> >>> >>>>>>>>>>>>>>>>>>> <pi...@gmail.com>
> >>> >>>>>>>>>>>>>>>>>>> Reply: dev@nifi.apache.org <
> >>> >>>> dev@nifi.apache.org>
> >>> >>>>> <
> >>> >>>>>>>>>>>>>>> dev@nifi.apache.org>
> >>> >>>>>>>>>>>>>>>>>>> Date: November 26, 2020 at 04:55:56
> >>> >>>>>>>>>>>>>>>>>>> To: dev@nifi.apache.org <de...@nifi.apache.org>
> >>> >>>> <
> >>> >>>>>>>>>>>>> dev@nifi.apache.org
> >>> >>>>>>>>>>>>>>>>
> >>> >>>>>>>>>>>>>>>>>>> Subject: [DISCUSS] Release of Apache NiFi
> >>> >>>> 1.13.0
> >>> >>>>>>>>>>>>>>>>>>>
> >>> >>>>>>>>>>>>>>>>>>> Hi community,
> >>> >>>>>>>>>>>>>>>>>>>
> >>> >>>>>>>>>>>>>>>>>>> Starting a discussion thread around the release
> >>> >>>>> of
> >>> >>>>>>>> NiFi
> >>> >>>>>>>>>>>>> 1.13.0. We
> >>> >>>>>>>>>>>>>>>>> added
> >>> >>>>>>>>>>>>>>>>>>> quite a lot of significant improvements and
> >>> >>>>>>>> features since
> >>> >>>>>>>>>>> the
> >>> >>>>>>>>>>>>>>> release
> >>> >>>>>>>>>>>>>>>>> of
> >>> >>>>>>>>>>>>>>>>>>> 1.12.1 - I see 143 JIRAs with 1.13.0 as the fix
> >>> >>>>>>>> version. I
> >>> >>>>>>>>>>>>> think it
> >>> >>>>>>>>>>>>>>>>> makes
> >>> >>>>>>>>>>>>>>>>>>> sense to consider a new release.
> >>> >>>>>>>>>>>>>>>>>>>
> >>> >>>>>>>>>>>>>>>>>>> Please share here the JIRAs with opened pull
> >>> >>>>>>>> requests that
> >>> >>>>>>>>>>> we
> >>> >>>>>>>>>>>>> would
> >>> >>>>>>>>>>>>>>>>> need to
> >>> >>>>>>>>>>>>>>>>>>> look at to make this release happen.
> >>> >>>>>>>>>>>>>>>>>>>
> >>> >>>>>>>>>>>>>>>>>>> Thanks,
> >>> >>>>>>>>>>>>>>>>>>> Pierre
> >>> >>>>>>>>>>>>>>>>>
> >>> >>>>>>>>>>>>>>>
> >>> >>>>>>>>>>>>>
> >>> >>>>>>>>>>>>
> >>> >>>>>>>>>>>
> >>> >>>>>>>>
> >>> >>>>>>>
> >>> >>>>>
> >>> >>>>
> >>> >>
> >>> >>
> >>>
> >>>
>
Re: [DISCUSS] Release of Apache NiFi 1.13.0
Posted by Joe Witt <jo...@gmail.com>.
Team
starting RC2. Joey Frazee noted "I noticed that
nifi-docker/dockermaven-stateless/pom.xml
and nifi-docker/docker-compose/docker-compose.yml in the source package and
tag are still using 1.13.0-SNAPSHOT" while looking at RC1. I have no
instructions/guidance on what to do with those as an RM and I've never
modified them before. If we're going to keep these in the build, and I
would advocate actually that we remove them, then someone needs to
determine the whole lifecycle of how to manage/maintain them and
document the steps for a RelMgr. The dockerhub module we do have guidance
for and they're currently correct.
Thanks
On Mon, Feb 1, 2021 at 10:14 AM Joe Witt <jo...@gmail.com> wrote:
> Team,
>
> Will put RC2 for 1.13 back up today hopefully. The fix is in for the
> issue that sank the release.
>
> Thanks
> Joe
>
> On Thu, Jan 28, 2021 at 8:18 AM Joe Witt <jo...@gmail.com> wrote:
>
>> Otto
>>
>> Truth is we dont know. We cannot readily test with the amazing matrix
>> that exists. So we are leaning toward ensuring recent versions work as
>> expected.
>>
>> The goal is java 8 and 11 broadly right now. But these internal changes
>> of exception types being used are brutal.
>>
>> Thanks
>>
>> On Thu, Jan 28, 2021 at 8:15 AM Otto Fowler <ot...@gmail.com>
>> wrote:
>>
>>> Thanks Joe,
>>>
>>> I’m started down that road right after I sent this. I’ll update when I
>>> know.
>>> I _have_ been building nifi with this jdk all along though.
>>>
>>> If there are jdk minimum requirements, should they be documented ( or
>>> are they and I missed it)?
>>>
>>> > On Jan 28, 2021, at 09:35, Joe Witt <jo...@gmail.com> wrote:
>>> >
>>> > Otto
>>> >
>>> > I dont know we can keep all variants of Java 8 happy. That one is
>>> nearly
>>> > three years old. I would say try with something more recent. It has
>>> been
>>> > pretty shocking how many api changes we have seen across these builds.
>>> >
>>> > Thanks
>>> >
>>> > On Thu, Jan 28, 2021 at 6:12 AM Otto Fowler <ot...@gmail.com>
>>> wrote:
>>> >
>>> >> I’m trying to validate RC-1 and I’m seeing this exception building /
>>> >> running tests
>>> >>
>>> >> [INFO] Running org.apache.nifi.processors.standard.TestListenTCP
>>> >> [ERROR] Tests run: 6, Failures: 1, Errors: 0, Skipped: 0, Time
>>> elapsed:
>>> >> 4.499 s <<< FAILURE! - in
>>> org.apache.nifi.processors.standard.TestListenTCP
>>> >> [ERROR]
>>> >>
>>> testTLSClientAuthRequiredAndClientCertNotProvided(org.apache.nifi.processors.standard.TestListenTCP)
>>> >> Time elapsed: 0.127 s <<< FAILURE!
>>> >> java.lang.AssertionError: unexpected exception type thrown;
>>> >> expected:<javax.net.ssl.SSLException> but
>>> was:<java.net.SocketException>
>>> >> at
>>> >>
>>> org.apache.nifi.processors.standard.TestListenTCP.testTLSClientAuthRequiredAndClientCertNotProvided(TestListenTCP.java:159)
>>> >> Caused by: java.net.SocketException: Connection reset
>>> >> at
>>> >>
>>> org.apache.nifi.processors.standard.TestListenTCP.runTCP(TestListenTCP.java:209)
>>> >> at
>>> >>
>>> org.apache.nifi.processors.standard.TestListenTCP.lambda$testTLSClientAuthRequiredAndClientCertNotProvided$0(TestListenTCP.java:160)
>>> >> at
>>> >>
>>> org.apache.nifi.processors.standard.TestListenTCP.testTLSClientAuthRequiredAndClientCertNotProvided(TestListenTCP.java:159)
>>> >>
>>> >>
>>> >>
>>> >> Apache Maven 3.6.3 (cecedd343002696d0abb50b32b541b8a6ba2883f)
>>> >> Maven home: /usr/local/Cellar/maven/3.6.3_1/libexec
>>> >> Java version: 1.8.0_171, vendor: Oracle Corporation, runtime:
>>> >> /Library/Java/JavaVirtualMachines/jdk1.8.0_171.jdk/Contents/Home/jre
>>> >> Default locale: en_US, platform encoding: UTF-8
>>> >> OS name: "mac os x", version: "10.16", arch: "x86_64", family: “mac"
>>> >>
>>> >>
>>> >>
>>> >>> On Jan 27, 2021, at 10:31, Joe Witt <jo...@gmail.com> wrote:
>>> >>>
>>> >>> ...in this brutal game of wach a mole another couple brittle tests
>>> have
>>> >>> emerged on the Java 11 line.
>>> >>> https://issues.apache.org/jira/browse/NIFI-8177 will get that looked
>>> >> into.
>>> >>> And I'm also seeing if for some reason adding a bit more
>>> horsepower/cpu
>>> >>> usage to the github tests will help. Things had been very stable for
>>> >> quite
>>> >>> a while until the update to the latest 11.0.10 azul jdk came out so
>>> kind
>>> >> of
>>> >>> strange the tests became less reliable then. Anyway dont want to
>>> initiate
>>> >>> the RC until things seem stable otherwise it makes the vote process
>>> more
>>> >>> difficult and further when the builds dont pass it makes the already
>>> >>> difficult task of staying apace with PRs more inivolved.
>>> >>>
>>> >>> Thanks
>>> >>>
>>> >>> On Wed, Jan 27, 2021 at 12:19 AM Pierre Villard <
>>> >> pierre.villard.fr@gmail.com>
>>> >>> wrote:
>>> >>>
>>> >>>> Awesome, thanks Joe!
>>> >>>>
>>> >>>> Le mer. 27 janv. 2021 à 10:16, Joe Witt <jo...@gmail.com> a
>>> écrit :
>>> >>>>
>>> >>>>> Team,
>>> >>>>>
>>> >>>>> Ok wow so the issue with build failures that emerged has been
>>> resolved
>>> >> it
>>> >>>>> appears thanks to a lot of effort by exceptionfactory. The other
>>> >>>> lingering
>>> >>>>> commits/PRs are in and I think most of what folks asked for in this
>>> >>>>> thread. I just put in a commit which drops a few older/less common
>>> >> nars
>>> >>>>> from convenience binary inclusion to get us back under the maximum
>>> size
>>> >>>>> again. And now I think we can initiate RC1 build for 1.13.0.
>>> >>>>>
>>> >>>>> That should be published in the AM.
>>> >>>>>
>>> >>>>> Thanks
>>> >>>>>
>>> >>>>> On Mon, Jan 25, 2021 at 6:40 AM Joe Witt <jo...@gmail.com>
>>> wrote:
>>> >>>>>
>>> >>>>>> Team,
>>> >>>>>>
>>> >>>>>> There is a TZ handling issue
>>> >>>>>> https://issues.apache.org/jira/browse/NIFI-8023 that needs a
>>> >>>> resolution
>>> >>>>>> and there is also a new issue that has emerged on Github
>>> Actions/CI
>>> >>>>>> https://github.com/apache/nifi/actions which is resulting in
>>> broken
>>> >>>>>> builds. This emerged in the latest Java 11 Azul release and in
>>> Github
>>> >>>>> CI.
>>> >>>>>> I've tried to replicate with no success on a local linux machine
>>> with
>>> >>>> the
>>> >>>>>> exact same JVM/version.
>>> >>>>>>
>>> >>>>>> Once these are wrapped I'll initiate the RC. Great work to all
>>> >>>> involved
>>> >>>>>> in helping get the release candidate this close.
>>> >>>>>>
>>> >>>>>> Thanks
>>> >>>>>> Joe
>>> >>>>>>
>>> >>>>>> On Thu, Jan 21, 2021 at 8:30 AM Joe Witt <jo...@gmail.com>
>>> wrote:
>>> >>>>>>
>>> >>>>>>> Team,
>>> >>>>>>>
>>> >>>>>>> A couple 1.13 tagged items still lingering. Going to either kick
>>> >> them
>>> >>>>>>> out or merge them and get going. Hopefully an RC today or
>>> tomorrow.
>>> >>>>>>>
>>> >>>>>>> Thanks
>>> >>>>>>>
>>> >>>>>>> On Wed, Jan 20, 2021 at 7:21 AM Mike Thomsen <
>>> mikerthomsen@gmail.com
>>> >>>
>>> >>>>>>> wrote:
>>> >>>>>>>
>>> >>>>>>>> Bug confirmed. Working on a PR now.
>>> >>>>>>>>
>>> >>>>>>>> On Wed, Jan 20, 2021 at 8:45 AM Mike Thomsen <
>>> >> mikerthomsen@gmail.com
>>> >>>>>
>>> >>>>>>>> wrote:
>>> >>>>>>>>>
>>> >>>>>>>>> This morning, I think I found a serious bug in
>>> PutCassandraRecord
>>> >>>> WRT
>>> >>>>>>>>> writing binary data to Cassandra. I'm debugging now. If it's
>>> >>>> really a
>>> >>>>>>>>> bug, I'd appreciate it if we could squeak a fix into 1.13.
>>> >>>>>>>>>
>>> >>>>>>>>> On Tue, Jan 19, 2021 at 9:54 AM Joe Witt <jo...@gmail.com>
>>> >>>> wrote:
>>> >>>>>>>>>>
>>> >>>>>>>>>> Team,
>>> >>>>>>>>>>
>>> >>>>>>>>>> I'm going to initiate RM processes for 1.13. I'll be watching
>>> >>>>>>>> closely for
>>> >>>>>>>>>> currently tagged 1.13 items to include. If anything is
>>> dragging
>>> >>>>>>>> I'll just
>>> >>>>>>>>>> remove it from 1.13 and we'll pick it up later. Other items
>>> that
>>> >>>>> get
>>> >>>>>>>>>> dev/reviewer traction before I cut the RC we can include. I
>>> will
>>> >>>>>>>>>> *probably/hopefully* start that process first thing tomorrow
>>> >>>>> morning.
>>> >>>>>>>>>>
>>> >>>>>>>>>>
>>> https://issues.apache.org/jira/projects/NIFI/versions/12348700
>>> >>>> is
>>> >>>>>>>> what i'm
>>> >>>>>>>>>> working from.
>>> >>>>>>>>>>
>>> >>>>>>>>>> Thanks
>>> >>>>>>>>>>
>>> >>>>>>>>>> On Fri, Jan 15, 2021 at 6:12 PM Waleed Aibany <
>>> >>>> walmut44@gmail.com>
>>> >>>>>>>> wrote:
>>> >>>>>>>>>>
>>> >>>>>>>>>>> Hi,
>>> >>>>>>>>>>>
>>> >>>>>>>>>>> I did rebase to this old PR
>>> >>>>>>>> https://github.com/apache/nifi/pull/4167
>>> >>>>>>>>>>> Is it possible to include it in 1.13.0
>>> >>>>>>>>>>>
>>> >>>>>>>>>>> Thank you
>>> >>>>>>>>>>>
>>> >>>>>>>>>>> On 2021/01/05 15:03:32, Pierre Villard <
>>> >>>>>>>> pierre.villard.fr@gmail.com>
>>> >>>>>>>>>>> wrote:
>>> >>>>>>>>>>>> Hi all,
>>> >>>>>>>>>>>>
>>> >>>>>>>>>>>> Happy new year to everyone, hope you all had a great time.
>>> >>>> I'm
>>> >>>>>>>> bumping
>>> >>>>>>>>>>> this
>>> >>>>>>>>>>>> thread up as I think it'd make a lot of sense to release
>>> NiFi
>>> >>>>>>>> 1.13.0. We
>>> >>>>>>>>>>>> have a ton of bug fixes and improvements that would be very
>>> >>>>>>>> useful for
>>> >>>>>>>>>>> our
>>> >>>>>>>>>>>> community.
>>> >>>>>>>>>>>>
>>> >>>>>>>>>>>> Let's try to see if there are any blockers for a release and
>>> >>>>>>>> start the
>>> >>>>>>>>>>>> process:
>>> >>>>>>>>>>>>
>>> >>>>>>>>>>>
>>> >>>>>>>>
>>> >>>>>
>>> >>>>
>>> >>
>>> https://issues.apache.org/jira/issues/?jql=project%20%3D%20NIFI%20AND%20resolution%20%3D%20Unresolved%20AND%20fixVersion%20%3D%201.13.0%20ORDER%20BY%20priority%20DESC%2C%20updated%20DESC
>>> >>>>>>>>>>>>
>>> >>>>>>>>>>>> Thanks!
>>> >>>>>>>>>>>>
>>> >>>>>>>>>>>>
>>> >>>>>>>>>>>> Le mar. 1 déc. 2020 à 14:49, Bryan Bende <bb...@gmail.com>
>>> >>>> a
>>> >>>>>>>> écrit :
>>> >>>>>>>>>>>>
>>> >>>>>>>>>>>>> Chris,
>>> >>>>>>>>>>>>>
>>> >>>>>>>>>>>>> The illegal reflective access warnings are expected when
>>> >>>>>>>> running on
>>> >>>>>>>>>>> Java
>>> >>>>>>>>>>>>> 11.
>>> >>>>>>>>>>>>>
>>> >>>>>>>>>>>>> The second warning about the provenance repo seems like a
>>> >>>>>>>> possible
>>> >>>>>>>>>>>>> issue due to some recent refactorings made for stateless,
>>> >>>> we
>>> >>>>>>>> should
>>> >>>>>>>>>>>>> take a look at that.
>>> >>>>>>>>>>>>>
>>> >>>>>>>>>>>>> Thanks,
>>> >>>>>>>>>>>>>
>>> >>>>>>>>>>>>> Bryan
>>> >>>>>>>>>>>>>
>>> >>>>>>>>>>>>> On Tue, Dec 1, 2020 at 3:58 AM Chris Sampson
>>> >>>>>>>>>>>>> <ch...@naimuri.com.invalid> wrote:
>>> >>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>> Just spotted the following during startup of NiFi
>>> >>>>>>>> 1.13.0-SNAPSHOT on
>>> >>>>>>>>>>> my
>>> >>>>>>>>>>>>>> local machine, which might be worth looking at (although
>>> >>>>>>>> I've not
>>> >>>>>>>>>>> deleted
>>> >>>>>>>>>>>>>> and re-created the binaries in a little while, so I could
>>> >>>>>>>> have
>>> >>>>>>>>>>> something
>>> >>>>>>>>>>>>>> wrong in my /lib folder or such):
>>> >>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>> 2020-12-01 08:52:48,382 ERROR [NiFi logging handler]
>>> >>>>>>>>>>>>> org.apache.nifi.StdErr
>>> >>>>>>>>>>>>>> WARNING: An illegal reflective access operation has
>>> >>>>> occurred
>>> >>>>>>>>>>>>>> 2020-12-01 08:52:48,383 ERROR [NiFi logging handler]
>>> >>>>>>>>>>>>> org.apache.nifi.StdErr
>>> >>>>>>>>>>>>>> WARNING: Illegal reflective access by
>>> >>>>>>>>>>>>>> com.sun.xml.bind.v2.runtime.reflect.opt.Injector
>>> >>>>>>>>>>>>>>
>>> >>>>>>>> (file:.../nifi-1.13.0-SNAPSHOT/lib/java11/jaxb-impl-2.3.0.jar)
>>> to
>>> >>>>>>>>>>> method
>>> >>>>>>>>>>>>>>
>>> >>>>>>>>
>>> java.lang.ClassLoader.defineClass(java.lang.String,byte[],int,int)
>>> >>>>>>>>>>>>>> 2020-12-01 08:52:48,383 ERROR [NiFi logging handler]
>>> >>>>>>>>>>>>> org.apache.nifi.StdErr
>>> >>>>>>>>>>>>>> WARNING: Please consider reporting this to the
>>> >>>> maintainers
>>> >>>>> of
>>> >>>>>>>>>>>>>> com.sun.xml.bind.v2.runtime.reflect.opt.Injector
>>> >>>>>>>>>>>>>> 2020-12-01 08:52:48,383 ERROR [NiFi logging handler]
>>> >>>>>>>>>>>>> org.apache.nifi.StdErr
>>> >>>>>>>>>>>>>> WARNING: Use --illegal-access=warn to enable warnings of
>>> >>>>>>>> further
>>> >>>>>>>>>>> illegal
>>> >>>>>>>>>>>>>> reflective access operations
>>> >>>>>>>>>>>>>> 2020-12-01 08:52:48,383 ERROR [NiFi logging handler]
>>> >>>>>>>>>>>>> org.apache.nifi.StdErr
>>> >>>>>>>>>>>>>> WARNING: All illegal access operations will be denied in
>>> >>>> a
>>> >>>>>>>> future
>>> >>>>>>>>>>> release
>>> >>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>> Also:
>>> >>>>>>>>>>>>>> 2020-12-01 08:52:52,486 WARN [main]
>>> >>>>>>>>>>>>>> o.a.n.n.StandardExtensionDiscoveringManager Failed to
>>> >>>>>>>> register
>>> >>>>>>>>>>> extension
>>> >>>>>>>>>>>>>> org.apache.nifi.provenance.VolatileProvenanceRepository
>>> >>>> due
>>> >>>>>>>> to:
>>> >>>>>>>>>>> Attempt
>>> >>>>>>>>>>>>> was
>>> >>>>>>>>>>>>>> made to load
>>> >>>>>>>> org.apache.nifi.provenance.VolatileProvenanceRepository
>>> >>>>>>>>>>> from
>>> >>>>>>>>>>>>>>
>>> >>>>>>>> org.apache.nifi:nifi-provenance-repository-nar:1.13.0-SNAPSHOT
>>> but
>>> >>>>>>>>>>> that
>>> >>>>>>>>>>>>>> class name is already loaded/registered from
>>> >>>>>>>>>>>>>> org.apache.nifi:nifi-stateless-nar:1.13.0-SNAPSHOT and
>>> >>>>>>>> multiple
>>> >>>>>>>>>>> versions
>>> >>>>>>>>>>>>>> are not supported for this type
>>> >>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>> These log messages appear just before the NAR extraction
>>> >>>>>>>> logs during
>>> >>>>>>>>>>>>>> instance startup.
>>> >>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>> Don't know whether these are things that should be fixed
>>> >>>>>>>> before
>>> >>>>>>>>>>> 1.13.0
>>> >>>>>>>>>>>>>> and/or have already been looked into, but figured I'd
>>> >>>>>>>> mention them so
>>> >>>>>>>>>>>>>> they're at least known about.
>>> >>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>> ---
>>> >>>>>>>>>>>>>> *Chris Sampson*
>>> >>>>>>>>>>>>>> IT Consultant
>>> >>>>>>>>>>>>>> chris.sampson@naimuri.com
>>> >>>>>>>>>>>>>> <https://www.naimuri.com/>
>>> >>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>> On Mon, 30 Nov 2020 at 18:50, Nissim Shiman
>>> >>>>>>>>>>> <ns...@yahoo.com.invalid>
>>> >>>>>>>>>>>>>> wrote:
>>> >>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>>> Hello Nifi Team,
>>> >>>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>>> NIFI-7738 [1]
>>> >>>> https://github.com/apache/nifi/pull/4563
>>> >>>>>>>>>>>>>>> has already been reviewed/tested by a fellow
>>> >>>> contributer
>>> >>>>>>>>>>>>>>> I would greatly appreciate a committer moving this to
>>> >>>>> main
>>> >>>>>>>> for
>>> >>>>>>>>>>> 1.13.0
>>> >>>>>>>>>>>>>>> Thanks,
>>> >>>>>>>>>>>>>>> Nissim Shiman
>>> >>>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>>> [1] https://issues.apache.org/jira/browse/NIFI-7738
>>> >>>>>>>>>>>>>>> On Sunday, November 29, 2020, 07:12:12 PM EST, Matt
>>> >>>>>>>> Burgess <
>>> >>>>>>>>>>>>>>> mattyb149@apache.org> wrote:
>>> >>>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>>> I just merged Mike's Cassandra DMC PR, reviewing the
>>> >>>>>>>> graph stuff
>>> >>>>>>>>>>> now.
>>> >>>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>>> I have a bunch of open PRs [1], I don't think any are
>>> >>>>>>>> blockers for
>>> >>>>>>>>>>>>>>> 1.13.0 but thought I'd take this opportunity to find
>>> >>>> some
>>> >>>>>>>>>>> reviewers :)
>>> >>>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>>> Regards,
>>> >>>>>>>>>>>>>>> Matt
>>> >>>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>>> [1] https://github.com/apache/nifi/pulls/mattyb149
>>> >>>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>>> On Sat, Nov 28, 2020 at 10:13 AM Phillip Grenier
>>> >>>>>>>>>>> <ph...@nifi.rocks>
>>> >>>>>>>>>>>>>>> wrote:
>>> >>>>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>>>> I wouldn't mind
>>> >>>>> https://github.com/apache/nifi/pull/4554
>>> >>>>>>>> making
>>> >>>>>>>>>>> it
>>> >>>>>>>>>>>>> in.
>>> >>>>>>>>>>>>>>> Have
>>> >>>>>>>>>>>>>>>> seen a couple more instances where people have
>>> >>>> created
>>> >>>>>>>> custom
>>> >>>>>>>>>>>>> processors
>>> >>>>>>>>>>>>>>> to
>>> >>>>>>>>>>>>>>>> work around this PR.
>>> >>>>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>>>> On Thu, Nov 26, 2020 at 11:10 AM Mike Thomsen <
>>> >>>>>>>>>>>>> mikerthomsen@gmail.com>
>>> >>>>>>>>>>>>>>>> wrote:
>>> >>>>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>>>>> Also, for most of us (committers and community
>>> >>>>>>>> members), it's a
>>> >>>>>>>>>>>>>>>>> holiday season so might be good to delay a release
>>> >>>> to
>>> >>>>>>>> early
>>> >>>>>>>>>>> January
>>> >>>>>>>>>>>>>>>>> anyway. Just a thought.
>>> >>>>>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>>>>> On Thu, Nov 26, 2020 at 11:08 AM Mike Thomsen <
>>> >>>>>>>>>>>>> mikerthomsen@gmail.com>
>>> >>>>>>>>>>>>>>>>> wrote:
>>> >>>>>>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>>>>>> https://github.com/apache/nifi/pull/4638 - This
>>> >>>> is
>>> >>>>>>>> a big
>>> >>>>>>>>>>>>> increase in
>>> >>>>>>>>>>>>>>>>>> graph functionality, and I want to give him a
>>> >>>>> chance
>>> >>>>>>>> to get
>>> >>>>>>>>>>> his
>>> >>>>>>>>>>>>> first
>>> >>>>>>>>>>>>>>>>>> contribution in with 1.13 (we may have some more
>>> >>>> of
>>> >>>>>>>> his work
>>> >>>>>>>>>>> we
>>> >>>>>>>>>>>>> can
>>> >>>>>>>>>>>>>>>>>> open source).
>>> >>>>>>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>>>>>> Matt's also reviewing some of my Cassandra and
>>> >>>>> graph
>>> >>>>>>>> tickets
>>> >>>>>>>>>>> as
>>> >>>>>>>>>>>>> well.
>>> >>>>>>>>>>>>>>>>>> I wouldn't call those **blockers**, but having
>>> >>>> the
>>> >>>>>>>> Cassandra
>>> >>>>>>>>>>> DMC
>>> >>>>>>>>>>>>>>> fully
>>> >>>>>>>>>>>>>>>>>> fleshed out would be nice.
>>> >>>>>>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>>>>>> On Thu, Nov 26, 2020 at 9:10 AM Otto Fowler <
>>> >>>>>>>>>>>>> ottobackwards@gmail.com
>>> >>>>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>>>>> wrote:
>>> >>>>>>>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>>>>>>> NIFI-7795
>>> >>>>>>>> https://github.com/apache/nifi/pull/4656
>>> >>>>>>>>>>>>>>>>>>> NIFI-7761
>>> >>>>> https://github.com/apache/nifi/pull/4513
>>> >>>>>>>>>>>>>>>>>>> NIFI-2072
>>> >>>>> https://github.com/apache/nifi/pull/4384
>>> >>>>>>>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>>>>>>> From: Pierre Villard <
>>> >>>>> pierre.villard.fr@gmail.com>
>>> >>>>>>>>>>>>>>>>>>> <pi...@gmail.com>
>>> >>>>>>>>>>>>>>>>>>> Reply: dev@nifi.apache.org <
>>> >>>> dev@nifi.apache.org>
>>> >>>>> <
>>> >>>>>>>>>>>>>>> dev@nifi.apache.org>
>>> >>>>>>>>>>>>>>>>>>> Date: November 26, 2020 at 04:55:56
>>> >>>>>>>>>>>>>>>>>>> To: dev@nifi.apache.org <de...@nifi.apache.org>
>>> >>>> <
>>> >>>>>>>>>>>>> dev@nifi.apache.org
>>> >>>>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>>>>>>> Subject: [DISCUSS] Release of Apache NiFi
>>> >>>> 1.13.0
>>> >>>>>>>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>>>>>>> Hi community,
>>> >>>>>>>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>>>>>>> Starting a discussion thread around the release
>>> >>>>> of
>>> >>>>>>>> NiFi
>>> >>>>>>>>>>>>> 1.13.0. We
>>> >>>>>>>>>>>>>>>>> added
>>> >>>>>>>>>>>>>>>>>>> quite a lot of significant improvements and
>>> >>>>>>>> features since
>>> >>>>>>>>>>> the
>>> >>>>>>>>>>>>>>> release
>>> >>>>>>>>>>>>>>>>> of
>>> >>>>>>>>>>>>>>>>>>> 1.12.1 - I see 143 JIRAs with 1.13.0 as the fix
>>> >>>>>>>> version. I
>>> >>>>>>>>>>>>> think it
>>> >>>>>>>>>>>>>>>>> makes
>>> >>>>>>>>>>>>>>>>>>> sense to consider a new release.
>>> >>>>>>>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>>>>>>> Please share here the JIRAs with opened pull
>>> >>>>>>>> requests that
>>> >>>>>>>>>>> we
>>> >>>>>>>>>>>>> would
>>> >>>>>>>>>>>>>>>>> need to
>>> >>>>>>>>>>>>>>>>>>> look at to make this release happen.
>>> >>>>>>>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>>>>>>> Thanks,
>>> >>>>>>>>>>>>>>>>>>> Pierre
>>> >>>>>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>
>>> >>>>>>>>>>>>
>>> >>>>>>>>>>>
>>> >>>>>>>>
>>> >>>>>>>
>>> >>>>>
>>> >>>>
>>> >>
>>> >>
>>>
>>>