Re: [ANNOUNCE] New Apache NiFi Committer Paul Grey

[Robert Fellows]

Congrats Paul!

On Wed, Mar 16, 2022 at 9:35 PM Joe Gresock  wrote:

> Congrats, Paul!
>
> On Wed, Mar 16, 2022 at 9:13 PM Kevin Doran 
> wrote:
>
> > Congrats Paul! We’ll deserved
> > 
> > From: Nathan Gough 
> > Sent: Wednesday, March 16, 2022 9:12:21 PM
> > To: dev@nifi.apache.org 
> > Subject: Re: [ANNOUNCE] New Apache NiFi Committer Paul Grey
> >
> > Congrats, Paul! Thanks for your contributions so far.
> >
> > On Wed, Mar 16, 2022 at 9:06 PM Marton Szasz  wrote:
> >
> > > Congratulations, Paul!
> > >
> > > On Thu, 17 Mar 2022 at 00:00, Joe Witt  wrote:
> > > >
> > > > Congrats and thanks!
> > > >
> > > > On Wed, Mar 16, 2022 at 4:55 PM gre...@yahoo.com.INVALID
> > > >  wrote:
> > > >
> > > > > Thanks much!  Next step is to do something about this "yahoo.com"
> > > email
> > > > > address...
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > On Wednesday, March 16, 2022, 06:46:02 PM EDT, David Handermann <
> > > > > exceptionfact...@apache.org> wrote:
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > Apache NiFi community,
> > > > >
> > > > > On behalf of the Apache NiFi PMC, I am very pleased to announce
> that
> > > Paul
> > > > > Grey
> > > > > has accepted the PMC's invitation to become a committer on the
> Apache
> > > NiFi
> > > > > project.
> > > > >
> > > > > Paul has contributed a number of pull requests and code reviews
> over
> > > the
> > > > > past year, improving project security and test stability in a
> number
> > of
> > > > > areas. We appreciate Paul's work and look forward to continued
> > > > > contributions!
> > > > >
> > > > > Welcome Paul, and congratulations!
> > > > >
> > >
> >
>
-- 
---
Rob Fellows

Re: [ANNOUNCE] New Apache NiFi Committer Paul Grey

[Joe Gresock]

Congrats, Paul!

On Wed, Mar 16, 2022 at 9:13 PM Kevin Doran  wrote:

> Congrats Paul! We’ll deserved
> 
> From: Nathan Gough 
> Sent: Wednesday, March 16, 2022 9:12:21 PM
> To: dev@nifi.apache.org 
> Subject: Re: [ANNOUNCE] New Apache NiFi Committer Paul Grey
>
> Congrats, Paul! Thanks for your contributions so far.
>
> On Wed, Mar 16, 2022 at 9:06 PM Marton Szasz  wrote:
>
> > Congratulations, Paul!
> >
> > On Thu, 17 Mar 2022 at 00:00, Joe Witt  wrote:
> > >
> > > Congrats and thanks!
> > >
> > > On Wed, Mar 16, 2022 at 4:55 PM gre...@yahoo.com.INVALID
> > >  wrote:
> > >
> > > > Thanks much!  Next step is to do something about this "yahoo.com"
> > email
> > > > address...
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > On Wednesday, March 16, 2022, 06:46:02 PM EDT, David Handermann <
> > > > exceptionfact...@apache.org> wrote:
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > Apache NiFi community,
> > > >
> > > > On behalf of the Apache NiFi PMC, I am very pleased to announce that
> > Paul
> > > > Grey
> > > > has accepted the PMC's invitation to become a committer on the Apache
> > NiFi
> > > > project.
> > > >
> > > > Paul has contributed a number of pull requests and code reviews over
> > the
> > > > past year, improving project security and test stability in a number
> of
> > > > areas. We appreciate Paul's work and look forward to continued
> > > > contributions!
> > > >
> > > > Welcome Paul, and congratulations!
> > > >
> >
>

Re: [ANNOUNCE] New Apache NiFi Committer Paul Grey

[Kevin Doran]

Congrats Paul! We’ll deserved

From: Nathan Gough 
Sent: Wednesday, March 16, 2022 9:12:21 PM
To: dev@nifi.apache.org 
Subject: Re: [ANNOUNCE] New Apache NiFi Committer Paul Grey

Congrats, Paul! Thanks for your contributions so far.

On Wed, Mar 16, 2022 at 9:06 PM Marton Szasz  wrote:

> Congratulations, Paul!
>
> On Thu, 17 Mar 2022 at 00:00, Joe Witt  wrote:
> >
> > Congrats and thanks!
> >
> > On Wed, Mar 16, 2022 at 4:55 PM gre...@yahoo.com.INVALID
> >  wrote:
> >
> > > Thanks much!  Next step is to do something about this "yahoo.com"
> email
> > > address...
> > >
> > >
> > >
> > >
> > >
> > >
> > > On Wednesday, March 16, 2022, 06:46:02 PM EDT, David Handermann <
> > > exceptionfact...@apache.org> wrote:
> > >
> > >
> > >
> > >
> > >
> > > Apache NiFi community,
> > >
> > > On behalf of the Apache NiFi PMC, I am very pleased to announce that
> Paul
> > > Grey
> > > has accepted the PMC's invitation to become a committer on the Apache
> NiFi
> > > project.
> > >
> > > Paul has contributed a number of pull requests and code reviews over
> the
> > > past year, improving project security and test stability in a number of
> > > areas. We appreciate Paul's work and look forward to continued
> > > contributions!
> > >
> > > Welcome Paul, and congratulations!
> > >
>

Re: [ANNOUNCE] New Apache NiFi Committer Paul Grey

[Nathan Gough]

Congrats, Paul! Thanks for your contributions so far.

On Wed, Mar 16, 2022 at 9:06 PM Marton Szasz  wrote:

> Congratulations, Paul!
>
> On Thu, 17 Mar 2022 at 00:00, Joe Witt  wrote:
> >
> > Congrats and thanks!
> >
> > On Wed, Mar 16, 2022 at 4:55 PM gre...@yahoo.com.INVALID
> >  wrote:
> >
> > > Thanks much!  Next step is to do something about this "yahoo.com"
> email
> > > address...
> > >
> > >
> > >
> > >
> > >
> > >
> > > On Wednesday, March 16, 2022, 06:46:02 PM EDT, David Handermann <
> > > exceptionfact...@apache.org> wrote:
> > >
> > >
> > >
> > >
> > >
> > > Apache NiFi community,
> > >
> > > On behalf of the Apache NiFi PMC, I am very pleased to announce that
> Paul
> > > Grey
> > > has accepted the PMC's invitation to become a committer on the Apache
> NiFi
> > > project.
> > >
> > > Paul has contributed a number of pull requests and code reviews over
> the
> > > past year, improving project security and test stability in a number of
> > > areas. We appreciate Paul's work and look forward to continued
> > > contributions!
> > >
> > > Welcome Paul, and congratulations!
> > >
>

Re: [ANNOUNCE] New Apache NiFi Committer Paul Grey

[Marton Szasz]

Congratulations, Paul!

On Thu, 17 Mar 2022 at 00:00, Joe Witt  wrote:
>
> Congrats and thanks!
>
> On Wed, Mar 16, 2022 at 4:55 PM gre...@yahoo.com.INVALID
>  wrote:
>
> > Thanks much!  Next step is to do something about this "yahoo.com" email
> > address...
> >
> >
> >
> >
> >
> >
> > On Wednesday, March 16, 2022, 06:46:02 PM EDT, David Handermann <
> > exceptionfact...@apache.org> wrote:
> >
> >
> >
> >
> >
> > Apache NiFi community,
> >
> > On behalf of the Apache NiFi PMC, I am very pleased to announce that Paul
> > Grey
> > has accepted the PMC's invitation to become a committer on the Apache NiFi
> > project.
> >
> > Paul has contributed a number of pull requests and code reviews over the
> > past year, improving project security and test stability in a number of
> > areas. We appreciate Paul's work and look forward to continued
> > contributions!
> >
> > Welcome Paul, and congratulations!
> >

Re: SplitContent doesn’t support regex?

[Phil H]

I dunno about a good implementation…

I did a similar extension of GetTCP to allow for a regex EOM rather than a
single byte. It works, but I don’t feel like it was done in the spirit of
the existing processor!

On Thu, 17 Mar 2022 at 09:12, Joe Witt  wrote:

> Phil
>
> I'd say if you have a good implementation in mind you should go for it.
> Sounds interesting.
>
> Thanks
>
> On Wed, Mar 16, 2022 at 3:59 PM Phil H  wrote:
>
> > Hi,
> >
> > This seems like an odd omission - aside from performance (presumably?) is
> > there a reason why there isn’t a regex option for the byte sequence? I
> need
> > one but thought I’d ask before I built my own.
> >
> > Thanks
> > Phil
> >
>

Re: [ANNOUNCE] New Apache NiFi Committer Paul Grey

[Joe Witt]

Congrats and thanks!

On Wed, Mar 16, 2022 at 4:55 PM gre...@yahoo.com.INVALID
 wrote:

> Thanks much!  Next step is to do something about this "yahoo.com" email
> address...
>
>
>
>
>
>
> On Wednesday, March 16, 2022, 06:46:02 PM EDT, David Handermann <
> exceptionfact...@apache.org> wrote:
>
>
>
>
>
> Apache NiFi community,
>
> On behalf of the Apache NiFi PMC, I am very pleased to announce that Paul
> Grey
> has accepted the PMC's invitation to become a committer on the Apache NiFi
> project.
>
> Paul has contributed a number of pull requests and code reviews over the
> past year, improving project security and test stability in a number of
> areas. We appreciate Paul's work and look forward to continued
> contributions!
>
> Welcome Paul, and congratulations!
>

Re: [ANNOUNCE] New Apache NiFi Committer Paul Grey

[gre...@yahoo.com.INVALID]

Thanks much!  Next step is to do something about this "yahoo.com" email 
address...






On Wednesday, March 16, 2022, 06:46:02 PM EDT, David Handermann 
 wrote: 





Apache NiFi community,

On behalf of the Apache NiFi PMC, I am very pleased to announce that Paul
Grey
has accepted the PMC's invitation to become a committer on the Apache NiFi
project.

Paul has contributed a number of pull requests and code reviews over the
past year, improving project security and test stability in a number of
areas. We appreciate Paul's work and look forward to continued
contributions!

Welcome Paul, and congratulations!

Re: SplitContent doesn’t support regex?

[Joe Witt]

Phil

I'd say if you have a good implementation in mind you should go for it.
Sounds interesting.

Thanks

On Wed, Mar 16, 2022 at 3:59 PM Phil H  wrote:

> Hi,
>
> This seems like an odd omission - aside from performance (presumably?) is
> there a reason why there isn’t a regex option for the byte sequence? I need
> one but thought I’d ask before I built my own.
>
> Thanks
> Phil
>

SplitContent doesn’t support regex?

[Phil H]

Hi,

This seems like an odd omission - aside from performance (presumably?) is
there a reason why there isn’t a regex option for the byte sequence? I need
one but thought I’d ask before I built my own.

Thanks
Phil

[ANNOUNCE] New Apache NiFi Committer Paul Grey

[David Handermann]

Apache NiFi community,

On behalf of the Apache NiFi PMC, I am very pleased to announce that Paul
Grey
has accepted the PMC's invitation to become a committer on the Apache NiFi
project.

Paul has contributed a number of pull requests and code reviews over the
past year, improving project security and test stability in a number of
areas. We appreciate Paul's work and look forward to continued
contributions!

Welcome Paul, and congratulations!

Re: [discuss] pulling together a NiFi 1.16

[Matt Burgess]

I'm all for bringing into the next RC, if something goes sideways
during the RC validation we can always take it back out.

-Matt

On Wed, Mar 16, 2022 at 5:39 PM Joe Witt  wrote:
>
> Team
>
> We will have RC3 now because of a regression.  But we also now have an
> interesting opportunity.
>
> With https://github.com/apache/nifi/pull/5870/files we could both build and
> run on Java 17.  The changes are largely about tests and such.  I'm
> inclined to pull this in during the rc process.  I encourage others to
> chime in/review/etc.. in case there are some strong reasons not to pull it
> in.
>
> Adding 'Java 17 now supported' would be quite a nice thing...
>
> Thanks
>
> On Thu, Mar 10, 2022 at 9:10 AM Joe Witt  wrote:
>
> > Team,
> >
> > Mike's PR got merged it looks like.
> >
> > I'm initiating 1.16 RC.  For all commits going forward please tag as fix
> > version 1.17
> > https://issues.apache.org/jira/projects/NIFI/versions/12351438
> >
> > If we have failed RC's i'll pull things into 1.16 as needed.
> >
> > Thanks
> >
> > On Wed, Mar 9, 2022 at 9:25 AM Joe Witt  wrote:
> >
> >> Mike
> >>
> >> I left a comment on the PR.  But as usual with these releases there are
> >> always things that are close/nearly there/just need a review/etc..  If that
> >> or anything else lands by the time the RC is generated then we're good.
> >>
> >> Thanks
> >>
> >> On Wed, Mar 9, 2022 at 9:21 AM Mike Thomsen 
> >> wrote:
> >>
> >>> Joe,
> >>>
> >>> I would like to see this review closed out before a 1.16 RC if
> >>> possible: https://github.com/apache/nifi/pull/4646 I think it's mainly
> >>> waiting on someone to verify that all of the changes have been made.
> >>>
> >>> Thanks,
> >>>
> >>> Mike
> >>>
> >>>
> >>> On Wed, Mar 9, 2022 at 10:54 AM Joe Witt  wrote:
> >>> >
> >>> > Mark
> >>> >
> >>> > The single user authorizer and default setup install is just to avoid
> >>> > having wide open systems by default.  So if you want to make changes to
> >>> > security settings and do it right you dont' use that mode.  Happy to
> >>> have
> >>> > improvements within that scope of intent but does not sound like
> >>> anything
> >>> > we'd wait for.  When it lands it lands.
> >>> >
> >>> > Thanks
> >>> >
> >>> > On Wed, Mar 9, 2022 at 8:49 AM Mark Bean 
> >>> wrote:
> >>> >
> >>> > > Joe,
> >>> > >
> >>> > > I just discovered an issue yesterday that might need attention
> >>> first. I
> >>> > > haven't investigated fully yet nor created a ticket because I don't
> >>> yet
> >>> > > fully understand it. However, it appears as though the
> >>> > > single-user-authorizer may not be behaving as intended. When I
> >>> updated
> >>> > > nifi.properties to swap the self-signed, auto-generated keystore and
> >>> > > truststore with "real" ones, single-user became _every_ user. My
> >>> suspicion
> >>> > > is that any user whose browser presents a cert that was signed by a
> >>> CA in
> >>> > > the truststore is allowed in - without even prompting for
> >>> > > username/password.
> >>> > >
> >>> > > It may be considered a configuration error to allow this to happen.
> >>> Still,
> >>> > > this seems like extremely dangerous behavior.
> >>> > >
> >>> > > -Mark
> >>> > >
> >>> > >
> >>> > > On Wed, Mar 9, 2022 at 10:42 AM Joe Witt  wrote:
> >>> > >
> >>> > > > Team
> >>> > > >
> >>> > > > We appear to be at a good point to start pulling together the
> >>> release
> >>> > > > candidate for 1.16.
> >>> > > >
> >>> > > > https://issues.apache.org/jira/projects/NIFI/versions/12350741
> >>> > > >
> >>> > > > I'm basically waiting for
> >>> > > https://issues.apache.org/jira/browse/NIFI-9761
> >>> > > > to land then will start pulling together the release.
> >>> > > >
> >>> > > > Thanks
> >>> > > >
> >>> > > > On Mon, Feb 14, 2022 at 11:18 AM Joe Witt 
> >>> wrote:
> >>> > > >
> >>> > > > > Eduardo
> >>> > > > >
> >>> > > > > Getting reviewers on the UI/rest/front-end are among the
> >>> toughest as
> >>> > > > > there just aren't as many of those folks.
> >>> > > > >
> >>> > > > > The reply from Pierre was probably most telling. It looks fine
> >>> but
> >>> > > > > many of us would pause to merge without knowing precisely what
> >>> the
> >>> > > > > implications are.  What happens on a taxed system with many
> >>> > > > > CSs...I''ll comment on the PR.
> >>> > > > >
> >>> > > > > Thanks
> >>> > > > > Joe
> >>> > > > >
> >>> > > > > On Mon, Feb 14, 2022 at 11:13 AM Eduardo Fontes
> >>> > > > >  wrote:
> >>> > > > > >
> >>> > > > > > Hi All,
> >>> > > > > >
> >>> > > > > > Is it possible to include
> >>> > > > > https://issues.apache.org/jira/browse/NIFI-8927
> >>> > > > > > in release 1.16?
> >>> > > > > > I've been asking for a review
> >>> > > https://github.com/apache/nifi/pull/5247
> >>> > > > > > since AUG/2021 and I don't understand why nobody did it. It's a
> >>> > > simple
> >>> > > > > and
> >>> > > > > > useful UI feature.
> >>> > > > > >
> >>> > > > > > Peace out.
> >>> > > > > > Eduardo Fontes
> >>> > > > >
> >>> > > >
> >>> > >
> >>>
> 

Re: [discuss] pulling together a NiFi 1.16

[Joe Witt]

Team

We will have RC3 now because of a regression.  But we also now have an
interesting opportunity.

With https://github.com/apache/nifi/pull/5870/files we could both build and
run on Java 17.  The changes are largely about tests and such.  I'm
inclined to pull this in during the rc process.  I encourage others to
chime in/review/etc.. in case there are some strong reasons not to pull it
in.

Adding 'Java 17 now supported' would be quite a nice thing...

Thanks

On Thu, Mar 10, 2022 at 9:10 AM Joe Witt  wrote:

> Team,
>
> Mike's PR got merged it looks like.
>
> I'm initiating 1.16 RC.  For all commits going forward please tag as fix
> version 1.17
> https://issues.apache.org/jira/projects/NIFI/versions/12351438
>
> If we have failed RC's i'll pull things into 1.16 as needed.
>
> Thanks
>
> On Wed, Mar 9, 2022 at 9:25 AM Joe Witt  wrote:
>
>> Mike
>>
>> I left a comment on the PR.  But as usual with these releases there are
>> always things that are close/nearly there/just need a review/etc..  If that
>> or anything else lands by the time the RC is generated then we're good.
>>
>> Thanks
>>
>> On Wed, Mar 9, 2022 at 9:21 AM Mike Thomsen 
>> wrote:
>>
>>> Joe,
>>>
>>> I would like to see this review closed out before a 1.16 RC if
>>> possible: https://github.com/apache/nifi/pull/4646 I think it's mainly
>>> waiting on someone to verify that all of the changes have been made.
>>>
>>> Thanks,
>>>
>>> Mike
>>>
>>>
>>> On Wed, Mar 9, 2022 at 10:54 AM Joe Witt  wrote:
>>> >
>>> > Mark
>>> >
>>> > The single user authorizer and default setup install is just to avoid
>>> > having wide open systems by default.  So if you want to make changes to
>>> > security settings and do it right you dont' use that mode.  Happy to
>>> have
>>> > improvements within that scope of intent but does not sound like
>>> anything
>>> > we'd wait for.  When it lands it lands.
>>> >
>>> > Thanks
>>> >
>>> > On Wed, Mar 9, 2022 at 8:49 AM Mark Bean 
>>> wrote:
>>> >
>>> > > Joe,
>>> > >
>>> > > I just discovered an issue yesterday that might need attention
>>> first. I
>>> > > haven't investigated fully yet nor created a ticket because I don't
>>> yet
>>> > > fully understand it. However, it appears as though the
>>> > > single-user-authorizer may not be behaving as intended. When I
>>> updated
>>> > > nifi.properties to swap the self-signed, auto-generated keystore and
>>> > > truststore with "real" ones, single-user became _every_ user. My
>>> suspicion
>>> > > is that any user whose browser presents a cert that was signed by a
>>> CA in
>>> > > the truststore is allowed in - without even prompting for
>>> > > username/password.
>>> > >
>>> > > It may be considered a configuration error to allow this to happen.
>>> Still,
>>> > > this seems like extremely dangerous behavior.
>>> > >
>>> > > -Mark
>>> > >
>>> > >
>>> > > On Wed, Mar 9, 2022 at 10:42 AM Joe Witt  wrote:
>>> > >
>>> > > > Team
>>> > > >
>>> > > > We appear to be at a good point to start pulling together the
>>> release
>>> > > > candidate for 1.16.
>>> > > >
>>> > > > https://issues.apache.org/jira/projects/NIFI/versions/12350741
>>> > > >
>>> > > > I'm basically waiting for
>>> > > https://issues.apache.org/jira/browse/NIFI-9761
>>> > > > to land then will start pulling together the release.
>>> > > >
>>> > > > Thanks
>>> > > >
>>> > > > On Mon, Feb 14, 2022 at 11:18 AM Joe Witt 
>>> wrote:
>>> > > >
>>> > > > > Eduardo
>>> > > > >
>>> > > > > Getting reviewers on the UI/rest/front-end are among the
>>> toughest as
>>> > > > > there just aren't as many of those folks.
>>> > > > >
>>> > > > > The reply from Pierre was probably most telling. It looks fine
>>> but
>>> > > > > many of us would pause to merge without knowing precisely what
>>> the
>>> > > > > implications are.  What happens on a taxed system with many
>>> > > > > CSs...I''ll comment on the PR.
>>> > > > >
>>> > > > > Thanks
>>> > > > > Joe
>>> > > > >
>>> > > > > On Mon, Feb 14, 2022 at 11:13 AM Eduardo Fontes
>>> > > > >  wrote:
>>> > > > > >
>>> > > > > > Hi All,
>>> > > > > >
>>> > > > > > Is it possible to include
>>> > > > > https://issues.apache.org/jira/browse/NIFI-8927
>>> > > > > > in release 1.16?
>>> > > > > > I've been asking for a review
>>> > > https://github.com/apache/nifi/pull/5247
>>> > > > > > since AUG/2021 and I don't understand why nobody did it. It's a
>>> > > simple
>>> > > > > and
>>> > > > > > useful UI feature.
>>> > > > > >
>>> > > > > > Peace out.
>>> > > > > > Eduardo Fontes
>>> > > > >
>>> > > >
>>> > >
>>>
>>

Re: nifi.apache.org website

[Matt Gilman]

Thanks Jon. The invite link for Slack is at the bottom of this page [1].

[1] https://nifi.apache.org/mailing_lists.html

On Wed, Mar 16, 2022 at 4:46 PM Jonathan Conti-Vock <
jonathan.contiv...@gmail.com> wrote:

> Thanks for the update Steven. Correct me if I'm wrong, but I'll need
> someone to invite me as a guest to follow along in the slack channel,
> correct? I would be happy to and interested in lending my UI/UX experience
> to this conversation.
>
> Cheers,
>
> Jon
>
> On Wed, Mar 16, 2022 at 3:39 PM Steven Matison 
> wrote:
>
> > Just a quick update on this thread.  Progress has been made and we have
> an
> > initial hugo framework able to run the current site.
> >
> > Please join us in follow on conversation in #apachenifiwebsite on slack!
> >
> >
> >
> > On Fri, Mar 11, 2022 at 8:25 AM Joe Witt  wrote:
> >
> > > done.  and added you
> > >
> > > On Fri, Mar 11, 2022 at 6:17 AM Steven Matison <
> steven.mati...@gmail.com
> > >
> > > wrote:
> > >
> > > > So glad there is such an interest in this.
> > > >
> > > > Can we move discussion into a slack channel dedicated to this topic?
> > > >
> > > > On Wed, Mar 9, 2022 at 2:47 PM Steven Matison <
> > steven.mati...@gmail.com>
> > > > wrote:
> > > >
> > > > > Sounds awesome, gimme some time to go through everything you guys
> > have
> > > > > shared.
> > > > >
> > > > >
> > > > >
> > > > > On Wed, Mar 9, 2022 at 2:28 PM Andrew Lim <
> > andrewlim.apa...@gmail.com>
> > > > > wrote:
> > > > >
> > > > >> Hi Steven,
> > > > >>
> > > > >> Excited by your interest in this! A Jira was created to migrate
> the
> > > NiFi
> > > > >> website to ASF git build/deploy [1]. I’ve been meaning to work on
> it
> > > but
> > > > >> haven’t had the cycles.
> > > > >>
> > > > >> In my research on static-site generators, Hugo [2] came up as a
> very
> > > > >> strong candidate especially due to its speed. There are 10 Apache
> > > > websites
> > > > >> that currently use Hugo [3]. Apache Jena is one of them and that
> > team
> > > > >> documented their migration steps on their wiki [4].
> > > > >>
> > > > >> Perhaps you could do some research and share your findings. If we
> > can
> > > > get
> > > > >> a working version of the current NiFi website in a chosen
> generator,
> > > we
> > > > can
> > > > >> get a Discuss thread going in the community similar to what Apache
> > > Jena
> > > > did
> > > > >> [5].
> > > > >>
> > > > >> I would love to help with the migration as well as a refresh of
> the
> > > > site!
> > > > >>
> > > > >> -Drew
> > > > >>
> > > > >>
> > > > >> [1] https://issues.apache.org/jira/browse/NIFI-6848 <
> > > > >> https://issues.apache.org/jira/browse/NIFI-6848>
> > > > >> [2] https://gohugo.io/ 
> > > > >> [3]
> > > > >>
> > >
> https://github.com/search?q=topic%3Ahugo+org%3Aapache=Repositories
> > > > <
> > > > >>
> https://github.com/search?q=topic:hugo+org:apache=Repositories
> > >
> > > > >> [4]
> > > > >>
> > > >
> > >
> >
> https://cwiki.apache.org/confluence/display/INFRA/How+Apache+Jena+migrated+from+the+CMS
> > > > >> <
> > > > >>
> > > >
> > >
> >
> https://cwiki.apache.org/confluence/display/INFRA/How+Apache+Jena+migrated+from+the+CMS
> > > > >> >
> > > > >> [5]
> > https://lists.apache.org/thread/tt4mm3phpkjxf7kc5hp3t006sob7ksqr
> > > <
> > > > >> https://lists.apache.org/thread/tt4mm3phpkjxf7kc5hp3t006sob7ksqr>
> > > > >>
> > > > >>
> > > > >> > On Mar 9, 2022, at 1:59 PM, David Handermann <
> > > > >> exceptionfact...@apache.org> wrote:
> > > > >> >
> > > > >> > Hi Steven,
> > > > >> >
> > > > >> > Thanks for your interest! This would also be a great opportunity
> > to
> > > > >> > streamline the HTML generation approach to use something like
> Hugo
> > > or
> > > > >> > similar static-site generation system.
> > > > >> >
> > > > >> > Regards,
> > > > >> > David Handermann
> > > > >> >
> > > > >> > On Wed, Mar 9, 2022 at 12:44 PM Joe Witt 
> > > wrote:
> > > > >> >
> > > > >> >> Steven
> > > > >> >>
> > > > >> >> To say this is super welcome is an understatement.  We
> definitely
> > > > need
> > > > >> the
> > > > >> >> facelift you mention and we need to get off the old website
> > > mechanism
> > > > >> and
> > > > >> >> onto the newer one the ASF wants projects using.  This would be
> > > > >> awesome!
> > > > >> >>
> > > > >> >> Thanks!
> > > > >> >>
> > > > >> >>
> > > > >> >> On Wed, Mar 9, 2022 at 11:40 AM Steven Matison <
> > > > >> steven.mati...@gmail.com>
> > > > >> >> wrote:
> > > > >> >>
> > > > >> >>> Hey Dev Team,
> > > > >> >>>
> > > > >> >>>  Is there any way I could assist with modernizing the
> > > > >> >> nifi.apache.org
> > > > >> >>> website?
> > > > >> >>>
> > > > >> >>> Its 2022 and I think a facelift is in order...  I have a ton
> of
> > > > >> >> experience
> > > > >> >>> with web-dev and super passionate about NiFi.  This would be
> > > > >> something I
> > > > >> >>> would love to be a part of.
> > > > >> >>>
> > > > >> >>> Thanks,
> > > > >> >>>
> > > > >> >>> Steven
> > > > >> >>>
> 

Re: nifi.apache.org website

[Jonathan Conti-Vock]

Thanks for the update Steven. Correct me if I'm wrong, but I'll need
someone to invite me as a guest to follow along in the slack channel,
correct? I would be happy to and interested in lending my UI/UX experience
to this conversation.

Cheers,

Jon

On Wed, Mar 16, 2022 at 3:39 PM Steven Matison 
wrote:

> Just a quick update on this thread.  Progress has been made and we have an
> initial hugo framework able to run the current site.
>
> Please join us in follow on conversation in #apachenifiwebsite on slack!
>
>
>
> On Fri, Mar 11, 2022 at 8:25 AM Joe Witt  wrote:
>
> > done.  and added you
> >
> > On Fri, Mar 11, 2022 at 6:17 AM Steven Matison  >
> > wrote:
> >
> > > So glad there is such an interest in this.
> > >
> > > Can we move discussion into a slack channel dedicated to this topic?
> > >
> > > On Wed, Mar 9, 2022 at 2:47 PM Steven Matison <
> steven.mati...@gmail.com>
> > > wrote:
> > >
> > > > Sounds awesome, gimme some time to go through everything you guys
> have
> > > > shared.
> > > >
> > > >
> > > >
> > > > On Wed, Mar 9, 2022 at 2:28 PM Andrew Lim <
> andrewlim.apa...@gmail.com>
> > > > wrote:
> > > >
> > > >> Hi Steven,
> > > >>
> > > >> Excited by your interest in this! A Jira was created to migrate the
> > NiFi
> > > >> website to ASF git build/deploy [1]. I’ve been meaning to work on it
> > but
> > > >> haven’t had the cycles.
> > > >>
> > > >> In my research on static-site generators, Hugo [2] came up as a very
> > > >> strong candidate especially due to its speed. There are 10 Apache
> > > websites
> > > >> that currently use Hugo [3]. Apache Jena is one of them and that
> team
> > > >> documented their migration steps on their wiki [4].
> > > >>
> > > >> Perhaps you could do some research and share your findings. If we
> can
> > > get
> > > >> a working version of the current NiFi website in a chosen generator,
> > we
> > > can
> > > >> get a Discuss thread going in the community similar to what Apache
> > Jena
> > > did
> > > >> [5].
> > > >>
> > > >> I would love to help with the migration as well as a refresh of the
> > > site!
> > > >>
> > > >> -Drew
> > > >>
> > > >>
> > > >> [1] https://issues.apache.org/jira/browse/NIFI-6848 <
> > > >> https://issues.apache.org/jira/browse/NIFI-6848>
> > > >> [2] https://gohugo.io/ 
> > > >> [3]
> > > >>
> > https://github.com/search?q=topic%3Ahugo+org%3Aapache=Repositories
> > > <
> > > >> https://github.com/search?q=topic:hugo+org:apache=Repositories
> >
> > > >> [4]
> > > >>
> > >
> >
> https://cwiki.apache.org/confluence/display/INFRA/How+Apache+Jena+migrated+from+the+CMS
> > > >> <
> > > >>
> > >
> >
> https://cwiki.apache.org/confluence/display/INFRA/How+Apache+Jena+migrated+from+the+CMS
> > > >> >
> > > >> [5]
> https://lists.apache.org/thread/tt4mm3phpkjxf7kc5hp3t006sob7ksqr
> > <
> > > >> https://lists.apache.org/thread/tt4mm3phpkjxf7kc5hp3t006sob7ksqr>
> > > >>
> > > >>
> > > >> > On Mar 9, 2022, at 1:59 PM, David Handermann <
> > > >> exceptionfact...@apache.org> wrote:
> > > >> >
> > > >> > Hi Steven,
> > > >> >
> > > >> > Thanks for your interest! This would also be a great opportunity
> to
> > > >> > streamline the HTML generation approach to use something like Hugo
> > or
> > > >> > similar static-site generation system.
> > > >> >
> > > >> > Regards,
> > > >> > David Handermann
> > > >> >
> > > >> > On Wed, Mar 9, 2022 at 12:44 PM Joe Witt 
> > wrote:
> > > >> >
> > > >> >> Steven
> > > >> >>
> > > >> >> To say this is super welcome is an understatement.  We definitely
> > > need
> > > >> the
> > > >> >> facelift you mention and we need to get off the old website
> > mechanism
> > > >> and
> > > >> >> onto the newer one the ASF wants projects using.  This would be
> > > >> awesome!
> > > >> >>
> > > >> >> Thanks!
> > > >> >>
> > > >> >>
> > > >> >> On Wed, Mar 9, 2022 at 11:40 AM Steven Matison <
> > > >> steven.mati...@gmail.com>
> > > >> >> wrote:
> > > >> >>
> > > >> >>> Hey Dev Team,
> > > >> >>>
> > > >> >>>  Is there any way I could assist with modernizing the
> > > >> >> nifi.apache.org
> > > >> >>> website?
> > > >> >>>
> > > >> >>> Its 2022 and I think a facelift is in order...  I have a ton of
> > > >> >> experience
> > > >> >>> with web-dev and super passionate about NiFi.  This would be
> > > >> something I
> > > >> >>> would love to be a part of.
> > > >> >>>
> > > >> >>> Thanks,
> > > >> >>>
> > > >> >>> Steven
> > > >> >>>
> > > >> >>
> > > >>
> > > >>
> > >
> >
>

Apache Nifi deployment is not displaying in the browser

[Segun Abifarin]

Hello Dev/Support ,

Kindly assist with the installation of apache nifi. I have spent more than
24hrs deploying apache nifi, it is deployed successfully, services are
running in docker but I can't view it in browser. I am getting the error
below;
System ErrorThe request contained an invalid host header [34.212.36.220:9443]
in the request [/nifi]. Check for request manipulation or third-party
intercept.Valid host headers are [empty] or:

   - 127.0.0.1
   - 127.0.0.1:9443
   - localhost
   - localhost:9443
   - [::1]
   - [::1]:9443
   - f5f81078e675
   - f5f81078e675:9443
   - 172.17.0.2
   - 172.17.0.2:9443

Kindly Assist.

Segun Abifarin

Re: nifi.apache.org website

[Steven Matison]

Just a quick update on this thread.  Progress has been made and we have an
initial hugo framework able to run the current site.

Please join us in follow on conversation in #apachenifiwebsite on slack!



On Fri, Mar 11, 2022 at 8:25 AM Joe Witt  wrote:

> done.  and added you
>
> On Fri, Mar 11, 2022 at 6:17 AM Steven Matison 
> wrote:
>
> > So glad there is such an interest in this.
> >
> > Can we move discussion into a slack channel dedicated to this topic?
> >
> > On Wed, Mar 9, 2022 at 2:47 PM Steven Matison 
> > wrote:
> >
> > > Sounds awesome, gimme some time to go through everything you guys have
> > > shared.
> > >
> > >
> > >
> > > On Wed, Mar 9, 2022 at 2:28 PM Andrew Lim 
> > > wrote:
> > >
> > >> Hi Steven,
> > >>
> > >> Excited by your interest in this! A Jira was created to migrate the
> NiFi
> > >> website to ASF git build/deploy [1]. I’ve been meaning to work on it
> but
> > >> haven’t had the cycles.
> > >>
> > >> In my research on static-site generators, Hugo [2] came up as a very
> > >> strong candidate especially due to its speed. There are 10 Apache
> > websites
> > >> that currently use Hugo [3]. Apache Jena is one of them and that team
> > >> documented their migration steps on their wiki [4].
> > >>
> > >> Perhaps you could do some research and share your findings. If we can
> > get
> > >> a working version of the current NiFi website in a chosen generator,
> we
> > can
> > >> get a Discuss thread going in the community similar to what Apache
> Jena
> > did
> > >> [5].
> > >>
> > >> I would love to help with the migration as well as a refresh of the
> > site!
> > >>
> > >> -Drew
> > >>
> > >>
> > >> [1] https://issues.apache.org/jira/browse/NIFI-6848 <
> > >> https://issues.apache.org/jira/browse/NIFI-6848>
> > >> [2] https://gohugo.io/ 
> > >> [3]
> > >>
> https://github.com/search?q=topic%3Ahugo+org%3Aapache=Repositories
> > <
> > >> https://github.com/search?q=topic:hugo+org:apache=Repositories>
> > >> [4]
> > >>
> >
> https://cwiki.apache.org/confluence/display/INFRA/How+Apache+Jena+migrated+from+the+CMS
> > >> <
> > >>
> >
> https://cwiki.apache.org/confluence/display/INFRA/How+Apache+Jena+migrated+from+the+CMS
> > >> >
> > >> [5] https://lists.apache.org/thread/tt4mm3phpkjxf7kc5hp3t006sob7ksqr
> <
> > >> https://lists.apache.org/thread/tt4mm3phpkjxf7kc5hp3t006sob7ksqr>
> > >>
> > >>
> > >> > On Mar 9, 2022, at 1:59 PM, David Handermann <
> > >> exceptionfact...@apache.org> wrote:
> > >> >
> > >> > Hi Steven,
> > >> >
> > >> > Thanks for your interest! This would also be a great opportunity to
> > >> > streamline the HTML generation approach to use something like Hugo
> or
> > >> > similar static-site generation system.
> > >> >
> > >> > Regards,
> > >> > David Handermann
> > >> >
> > >> > On Wed, Mar 9, 2022 at 12:44 PM Joe Witt 
> wrote:
> > >> >
> > >> >> Steven
> > >> >>
> > >> >> To say this is super welcome is an understatement.  We definitely
> > need
> > >> the
> > >> >> facelift you mention and we need to get off the old website
> mechanism
> > >> and
> > >> >> onto the newer one the ASF wants projects using.  This would be
> > >> awesome!
> > >> >>
> > >> >> Thanks!
> > >> >>
> > >> >>
> > >> >> On Wed, Mar 9, 2022 at 11:40 AM Steven Matison <
> > >> steven.mati...@gmail.com>
> > >> >> wrote:
> > >> >>
> > >> >>> Hey Dev Team,
> > >> >>>
> > >> >>>  Is there any way I could assist with modernizing the
> > >> >> nifi.apache.org
> > >> >>> website?
> > >> >>>
> > >> >>> Its 2022 and I think a facelift is in order...  I have a ton of
> > >> >> experience
> > >> >>> with web-dev and super passionate about NiFi.  This would be
> > >> something I
> > >> >>> would love to be a part of.
> > >> >>>
> > >> >>> Thanks,
> > >> >>>
> > >> >>> Steven
> > >> >>>
> > >> >>
> > >>
> > >>
> >
>

[CANCEL][VOTE] Release Apache NiFi 1.16.0 (rc2)

[Joe Witt]

RC2 is cancelled.

On Wed, Mar 16, 2022 at 11:46 AM David Handermann <
exceptionfact...@apache.org> wrote:

> -1 (binding)
>
> In light of a problem just reported with AccessToken.isExpired()
> determination in the StandardOauth2TokenProvider service, this issue should
> be corrected:
>
> https://issues.apache.org/jira/browse/NIFI-9801
>
> Regards,
> David Handermann
>
> On Wed, Mar 16, 2022 at 12:05 PM Mark Payne  wrote:
>
> > +1 (binding)
> >
> > - Performed full build with contib-chck
> > - Veified the hashes
> > - Ran all system tests successfully
> > - Started up and loaded a large flow with thousdands of processors.
> > Ensured that all loaded successfully.
> > - Ran some smoke screen tests
> > - Ran several tests with disconnecting nodes, updated flow, ensuring that
> > node could join back and properly inherited all changes
> >
> > Thanks
> > -Mark
> >
> >
> > > On Mar 15, 2022, at 4:17 PM, Joe Witt  wrote:
> > >
> > > Hello,
> > >
> > > I am pleased to be calling this vote for the source release of Apache
> > NiFi
> > > 1.16.0.
> > >
> > > The source zip, including signatures, digests, etc. can be found at:
> > > https://repository.apache.org/content/repositories/orgapachenifi-1197
> > >
> > > The source being voted upon and the convenience binaries can be found
> at:
> > > https://dist.apache.org/repos/dist/dev/nifi/nifi-1.16.0/
> > >
> > > A helpful reminder on how the release candidate verification process
> > works:
> > >
> >
> https://cwiki.apache.org/confluence/display/NIFI/How+to+help+verify+an+Apache+NiFi+release+candidate
> > >
> > > The Git tag is nifi-1.16.0-RC2
> > > The Git commit ID is a680b3f093fc93197036fb43c08e75f6a3f21a18
> > >
> >
> https://gitbox.apache.org/repos/asf?p=nifi.git;a=commit;h=a680b3f093fc93197036fb43c08e75f6a3f21a18
> > >
> > > Checksums of nifi-1.16.0-source-release.zip:
> > > SHA256:
> 02c03615df5be60958717471e40ca97d1b47457ef7355e056b385e3384cb54f2
> > > SHA512:
> > >
> >
> 43e9baa695b9617999d88f4d5878775d37bc293747c0cd6bcb1fc77318fca07bde5c5c536cc273937593c0194dd25426a617137861832b1b3749307eb2b9fd70
> > >
> > > Release artifacts are signed with the following key:
> > > https://people.apache.org/keys/committer/joewitt.asc
> > >
> > > KEYS file available here:
> > > https://dist.apache.org/repos/dist/release/nifi/KEYS
> > >
> > > 387 issues were closed/resolved for this release:
> > >
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020=12350741
> > >
> > > Release note highlights can be found here:
> > >
> >
> https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version1.16.0
> > >
> > > The vote will be open for 72 hours.
> > > Please download the release candidate and evaluate the necessary items
> > > including checking hashes, signatures, build from source, and test.
> Then
> > > please vote:
> > >
> > > [ ] +1 Release this package as nifi-1.16.0
> > > [ ] +0 no opinion
> > > [ ] -1 Do not release this package because...
> >
> >
>

Re: [VOTE] Release Apache NiFi 1.16.0 (rc2)

[David Handermann]

-1 (binding)

In light of a problem just reported with AccessToken.isExpired()
determination in the StandardOauth2TokenProvider service, this issue should
be corrected:

https://issues.apache.org/jira/browse/NIFI-9801

Regards,
David Handermann

On Wed, Mar 16, 2022 at 12:05 PM Mark Payne  wrote:

> +1 (binding)
>
> - Performed full build with contib-chck
> - Veified the hashes
> - Ran all system tests successfully
> - Started up and loaded a large flow with thousdands of processors.
> Ensured that all loaded successfully.
> - Ran some smoke screen tests
> - Ran several tests with disconnecting nodes, updated flow, ensuring that
> node could join back and properly inherited all changes
>
> Thanks
> -Mark
>
>
> > On Mar 15, 2022, at 4:17 PM, Joe Witt  wrote:
> >
> > Hello,
> >
> > I am pleased to be calling this vote for the source release of Apache
> NiFi
> > 1.16.0.
> >
> > The source zip, including signatures, digests, etc. can be found at:
> > https://repository.apache.org/content/repositories/orgapachenifi-1197
> >
> > The source being voted upon and the convenience binaries can be found at:
> > https://dist.apache.org/repos/dist/dev/nifi/nifi-1.16.0/
> >
> > A helpful reminder on how the release candidate verification process
> works:
> >
> https://cwiki.apache.org/confluence/display/NIFI/How+to+help+verify+an+Apache+NiFi+release+candidate
> >
> > The Git tag is nifi-1.16.0-RC2
> > The Git commit ID is a680b3f093fc93197036fb43c08e75f6a3f21a18
> >
> https://gitbox.apache.org/repos/asf?p=nifi.git;a=commit;h=a680b3f093fc93197036fb43c08e75f6a3f21a18
> >
> > Checksums of nifi-1.16.0-source-release.zip:
> > SHA256: 02c03615df5be60958717471e40ca97d1b47457ef7355e056b385e3384cb54f2
> > SHA512:
> >
> 43e9baa695b9617999d88f4d5878775d37bc293747c0cd6bcb1fc77318fca07bde5c5c536cc273937593c0194dd25426a617137861832b1b3749307eb2b9fd70
> >
> > Release artifacts are signed with the following key:
> > https://people.apache.org/keys/committer/joewitt.asc
> >
> > KEYS file available here:
> > https://dist.apache.org/repos/dist/release/nifi/KEYS
> >
> > 387 issues were closed/resolved for this release:
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020=12350741
> >
> > Release note highlights can be found here:
> >
> https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version1.16.0
> >
> > The vote will be open for 72 hours.
> > Please download the release candidate and evaluate the necessary items
> > including checking hashes, signatures, build from source, and test. Then
> > please vote:
> >
> > [ ] +1 Release this package as nifi-1.16.0
> > [ ] +0 no opinion
> > [ ] -1 Do not release this package because...
>
>

Re: [VOTE] Release Apache NiFi 1.16.0 (rc2)

[Mark Payne]

+1 (binding)

- Performed full build with contib-chck
- Veified the hashes
- Ran all system tests successfully
- Started up and loaded a large flow with thousdands of processors. Ensured 
that all loaded successfully.
- Ran some smoke screen tests
- Ran several tests with disconnecting nodes, updated flow, ensuring that node 
could join back and properly inherited all changes

Thanks
-Mark


> On Mar 15, 2022, at 4:17 PM, Joe Witt  wrote:
> 
> Hello,
> 
> I am pleased to be calling this vote for the source release of Apache NiFi
> 1.16.0.
> 
> The source zip, including signatures, digests, etc. can be found at:
> https://repository.apache.org/content/repositories/orgapachenifi-1197
> 
> The source being voted upon and the convenience binaries can be found at:
> https://dist.apache.org/repos/dist/dev/nifi/nifi-1.16.0/
> 
> A helpful reminder on how the release candidate verification process works:
> https://cwiki.apache.org/confluence/display/NIFI/How+to+help+verify+an+Apache+NiFi+release+candidate
> 
> The Git tag is nifi-1.16.0-RC2
> The Git commit ID is a680b3f093fc93197036fb43c08e75f6a3f21a18
> https://gitbox.apache.org/repos/asf?p=nifi.git;a=commit;h=a680b3f093fc93197036fb43c08e75f6a3f21a18
> 
> Checksums of nifi-1.16.0-source-release.zip:
> SHA256: 02c03615df5be60958717471e40ca97d1b47457ef7355e056b385e3384cb54f2
> SHA512:
> 43e9baa695b9617999d88f4d5878775d37bc293747c0cd6bcb1fc77318fca07bde5c5c536cc273937593c0194dd25426a617137861832b1b3749307eb2b9fd70
> 
> Release artifacts are signed with the following key:
> https://people.apache.org/keys/committer/joewitt.asc
> 
> KEYS file available here:
> https://dist.apache.org/repos/dist/release/nifi/KEYS
> 
> 387 issues were closed/resolved for this release:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020=12350741
> 
> Release note highlights can be found here:
> https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version1.16.0
> 
> The vote will be open for 72 hours.
> Please download the release candidate and evaluate the necessary items
> including checking hashes, signatures, build from source, and test. Then
> please vote:
> 
> [ ] +1 Release this package as nifi-1.16.0
> [ ] +0 no opinion
> [ ] -1 Do not release this package because...

Re: Jira Contributor Access

[Pat Alwell]

Wicked thanks Arpad!

Pat Alwell
Backend Engineer - Cloud
pat.alw...@gmail.com | (540)226-7365 | www.patalwell.com



> On Mar 16, 2022, at 03:39, Arpad Boda  wrote:
> 
> Hey Pat,
> 
> Granted, looking forward to your PRs!
> 
> Cheers,
> Arpad
> 
>> On Wed, Mar 16, 2022 at 2:35 AM Patrick Alwell, Jr. 
>> wrote:
>> 
>> Hey Guys,
>> 
>> Requesting  Jira Access for contributing to NiFi.
>> 
>> Username = pat_alwell
>> 
>> Found a few small bugs and created patches, so will open tickets and get a
>> few PRs over to ya!
>> 
>> -Pat

Re: Jira Contributor Access

[Arpad Boda]

Hey Pat,

Granted, looking forward to your PRs!

Cheers,
Arpad

On Wed, Mar 16, 2022 at 2:35 AM Patrick Alwell, Jr. 
wrote:

> Hey Guys,
>
> Requesting  Jira Access for contributing to NiFi.
>
> Username = pat_alwell
>
> Found a few small bugs and created patches, so will open tickets and get a
> few PRs over to ya!
>
> -Pat