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
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
Found some helpful info:
https://infra.apache.org/project-site.html#default
Thanks,
-Original Message-
From: David Handermann
Sent: Wednesday, March 9, 2022 2:00 PM
To: dev@nifi.apache.org
Subject: Re: nifi.apache.org website
Hi Steven,
Thanks for your interest! This would also be a
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
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
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
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,
>
>
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
Mark,
To elaborate on Joe's reply, changing the trust store configuration alters
the security profile of NiFi by allowing clients with trusted certificates
to access the system. Changing the key store and trust store should always
occur in conjunction with changing the authorization
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
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
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
Hi Grant,
FlowFiles in NiFI are accessed transactionally. This transactionality is
provided by the ProcessSession.
So the transfer() method cannot put the FlowFIles on the next queue, as the
session may be rolled back
afterwards. You’ll want to see the StandardProcessSessin’s commit() method.
Hi,
I am new to Nifi. I am investigating the source code by running the simple
Syslog example(
https://cwiki.apache.org/confluence/download/attachments/57904847/SyslogExample.xml?version=1=1446737325000=v2
)
In "ListenSyslog" processor, I saw this line: "session.transfer(flowFile,
REL_SUCCESS)",
14 matches
Mail list logo
