I believe this is what we're already doing for NiFi Registry and its
supported databases:
https://github.com/apache/nifi/tree/main/nifi-registry/nifi-registry-core/nifi-registry-test
Pierre
Le mer. 28 sept. 2022 à 19:22, Mike Thomsen a
écrit :
> We've been successfully using testcontainers (the
+1 binding
went through the usual steps, deployed a secured cluster with secured NiFi
Registry, executed my usual flows, everything is looking good
Thanks Joe for taking care of this release!
Le ven. 29 juil. 2022 à 14:06, Robert Fellows a
écrit :
> +1 (non-binding)
>
> Ran through the release
+1 (binding)
Went through the usual steps and deployed a secured cluster with secured
NiFi Registry to run some flows.
Built on Mac OS Monterey 12.4
Apache Maven 3.8.2 (ea98e05a04480131370aa0c110b8c54cf726c06f)
Java version: 1.8.0_302, vendor: Azul Systems, Inc., runtime:
/Library/Java/JavaVirtua
An option is to set the destination of the reporting task to
https://${hostname(true)}:PortNumber so
that expression language is used to get the hostname of the node. Based on
your warning message, this is a network issue so using the local FQDN may
be better.
Le jeu. 14 juil. 2022 à 20:17, a
écr
Hi,
Monitoring in NiFi is one of my favorite topics and I do think
OpenTelemetry would be of great value. There is never too much
observability in a software like NiFi when it comes to integrating anything
with anything. I'm more than happy to be part of the discussion in terms of
requirements/imp
I'd even love to go straight to Java 17 since it's the new LTS version...
but this may be quite a big jump for our community and users.
I guess we can envision a "short" 2.x release line and consider Java 17 for
3.x.
Definitely approve the proposal!
Le mer. 15 juin 2022 à 18:50, Kevin Doran a écr
+1 (binding)
Went through the usual steps (build, signature, etc) and deployed a secured
NiFi cluster and NiFi Registry in GCP.
Thanks Joe for taking care of this release!
Thanks,
Pierre
Le mar. 14 juin 2022 à 17:19, Adam Debreceni a
écrit :
> +1 (non-binding)
>
> Verified signature, hashes.
>
+1
Le mar. 17 mai 2022 à 10:02, Ádám Markovics a écrit :
> Hi,
> I also think it's time for a new release.
> Regards,
>
> Ádám
>
> On Mon, May 16, 2022 at 5:32 PM Marton Szasz wrote:
>
> > I agree that it's time for a new release, thanks for RM'ing Martin.
> >
> > I have these two issues that I
+1 (binding)
Went through the usual steps. Deployed a secured cluster with secured NiFi
Registry in GCP. Deployed usual/common flows. Looking good to me.
Thanks Joe for taking care of this release.
Pierre
Le jeu. 28 avr. 2022 à 00:52, Peter Turcsanyi a
écrit :
> +1 (non-binding)
>
> Ran throu
Hi Dharani,
I confirm that NiFi 1.16.0 has been released a few weeks ago now and we're
about to start the release process for a 1.16.1 release. I'd recommend
waiting for this release if you can, it should be available by next week I
think (no promises though).
Thanks,
Pierre
Le mar. 19 avr. 2022
Congrats Adam!
Le lun. 28 mars 2022 à 16:11, Kevin Doran a écrit :
> Congrats, Adam!
>
> On Mar 28, 2022 at 10:08:24, Otto Fowler wrote:
>
> > Congratulations!
> >
> > From: Marton Szasz
> > Reply: dev@nifi.apache.org
> > Date: March 25, 2022 at 08:50:07
> > To: dev@nifi.apache.org
> > S
+1 (binding)
Went through the usual steps.
Thanks Joe!
Le mar. 18 janv. 2022 à 04:27, Joe Gresock a écrit :
> +1 (non-binding)
>
> Verified signatures and hashes, built from source (MacOS 11.6, Azul Zulu
> 1.8.0_292), ran a 3-node cluster and some basic flows.
>
> On Mon, Jan 17, 2022 at 6:20
+1 (binding)
Went through the usual steps and confirmed the use of the correct log4j
transitive dependencies.
Thanks for taking care of the release Joe.
Pierre
Le mer. 22 déc. 2021 à 11:17, Kotaro Terada a écrit :
> +1 (non-binding)
>
> - Verified signatures and hashes.
> - Built from source
Congrats Margot!
Le mer. 15 déc. 2021 à 20:00, Kevin Doran a écrit :
> Congratulations Margot! Well deserved.
>
> > On Dec 15, 2021, at 13:47, Joe Witt wrote:
> >
> > Congrats Margot! And thanks
> >
> > On Wed, Dec 15, 2021 at 11:46 AM Matt Gilman
> wrote:
> >
> >> Apache NiFi community,
> >
+1 (binding)
Went through the usual steps.
Thanks for taking care of this so quickly!
Pierre
Le mer. 15 déc. 2021 à 10:55, Kotaro Terada a écrit :
> +1 (non-binding)
>
> - Verified signatures and hashes.
> - Built from source with OpenJDK 8 and OpenJDK 11.
> - Ran and tested a couple of flows.
https://issues.apache.org/jira/browse/NIFI-9482
Le mer. 15 déc. 2021 à 09:44, Ganesh, B (Nokia - IN/Bangalore) <
b.gan...@nokia.com> a écrit :
> Hi All ,
>
> According to latest mitigation plan from Log4J - (
> https://logging.apache.org/log4j/2.x/security.html) Java 8 (or later)
> users should
+1 binding
Went through the usual steps, built sources and tested a simple flow.
Le mar. 7 déc. 2021 à 10:53, Ferenc Gerlits a écrit :
> +1 (non-binding)
>
> - checked signatures and hashes
> - compared the source to the tag in the repo
> - connected to C2 using TLS
> - ran a simple GetFile ->
+1 (binding)
Le mer. 1 déc. 2021 à 20:30, Otto Fowler a écrit :
> +1 (non-binding)
> ran through the testing guide
>
> From: Bryan Bende
> Reply: dev@nifi.apache.org
> Date: November 30, 2021 at 15:56:38
> To: dev@nifi.apache.org
> Subject: [VOTE] Release Apache NiFi NAR Maven Plugin 1.3
+1 (binding)
Followed the usual steps to build the agent on my MBP and test it with a
simple flow.
Thanks Adam for taking care of this release!
Pierre
Le mer. 24 nov. 2021 à 10:49, Ádám Markovics a
écrit :
> +1 (non-binding)
> Verified and built on Ubuntu 20.04. Ran tests and also ran a simpl
rrectly and gives the same error
> :(
>
> To summarize the situation, this error only happens in NiFi 1.14.0 and
> 1.15.0 versions.
>
> Could you help in order to resolve this situation?
>
> Thank you in advance,
>
> --Bilal
>
>
>
> -Original Message
Hi team,
I'd like to discuss the possibility to change the release process we have
for the next releases so that the documentation of all components we have
in the repository are published as part of the release process.
All of the documentation for components that are in specific profiles are
no
+1 (binding)
Went through the usual steps, deployed a secured cluster with NiFi Registry
on GCP, both configured with OIDC and using Azul JDK 11. Tested some of the
new features and bug fixes. Looking good, this contains a lot of great
stuff!
Thanks for taking care of the release process Joe
Tha
Hi,
What information do you need on the parent? What's the intent?
The bulletin provides the group path with the chain of all the process
groups leading to the component where the bulletin is generated.
Thanks,
Pierre
Le mer. 27 oct. 2021 à 03:49, Jairo Henao a
écrit :
> Hello community,
>
> I
Hi Daniel, the images are available here:
https://hub.docker.com/r/apache/nifi-minifi (MiNiFi Java)
https://hub.docker.com/r/apache/nifi-minifi-cpp (MiNiFi C++)
MiNiFi Java has not been updated in a while because we merged the MiNiFi
Java code into NiFi and it's now a NiFi headless version. I beli
Congrats David, well deserved!!
Le sam. 18 sept. 2021 à 00:36, David Handermann
a écrit :
> Thank you all for the congratulations! After using NiFi for several years,
> it is great to be able to contribute back. I look forward to continued
> involvement on a great project with a great group of
s I mentioned in my previous email, this error happens only in NiFi
> 1.14.0 version.
>
> Thank you for helping,
>
> --Bilal
>
>
> -Original Message-
> From: Pierre Villard
> Sent: 15 Eylül 2021 Çarşamba 13:50
> To: dev@nifi.apache.org
> Subject: Re: [SPAM]
Hi,
Is there something you changed on how the Snappy libraries are loaded in
the NiFi JVM?
I'm not familiar with this specifically but you may need more recent
versions of the native libraries.
Also, anything related to a snappy-java lib you added somewhere? /lib?
custom processor? etc.
I believe
data structure for their application.
>
> I have known that FIWARE community is very interested in contributing to
> this development. Can we start a discussion over this topic?.
>
> Best Regards,
>
> Andrés
>
>
>
> > El 8 sept 2021, a las 13:29, Pierre Villard
Hi,
I just had a quick look and you propose a processor that is receiving the
notifications and sending the data into Postgres. Instead, isn't it better
to leverage NiFi to receive the notifications, turn these into FlowFiles
and let users decide what processors they should use next? This way they
Filed https://issues.apache.org/jira/browse/NIFI-8951
and submitted https://github.com/apache/nifi/pull/5256
Thanks,
Pierre
Le mer. 28 juil. 2021 à 12:19, Pierre Villard
a écrit :
> Hi Bilal,
>
> Your observation is correct, I'll file a JIRA and fix this. Thanks for
> reporti
Hi Bilal,
Your observation is correct, I'll file a JIRA and fix this. Thanks for
reporting it.
Thanks,
Pierre
Le mer. 28 juil. 2021 à 11:36, Bilal Bektas a
écrit :
> Hi Dev Team,
>
>
>
> “Default Decimal Scale” which is one of the properties of
> QueryDatabaseTable has worked correctly before
nt.days=3
>
> nifi.status.repository.questdb.persist.location=../repositories/status_repository
>
> On Fri, Jul 23, 2021 at 12:57 PM Pierre Villard <
> pierre.villard...@gmail.com> wrote:
>
>> Hi Eduardo,
>>
>> The image didn't go through. Also can you
Hi Eduardo,
The image didn't go through. Also can you share your nifi.properties
configuration related to status history configuration.
Thanks,
Pierre
Le ven. 23 juil. 2021 à 17:00, Eduardo Fontes a
écrit :
> Hi all,
>
> I have a 3 node NiFi 1.14 Cluster, Java 11, CentOS 7
>
> I've started it
a HUGE +1 (binding)
This is a great move forward to land many new features in NiFi.
Le ven. 16 juil. 2021 à 20:26, David Handermann
a écrit :
> Thanks for handling this, Matt. As one of the reviewers on the PR, I vote
> +1 (non-binding).
>
> Regards,
> David Handermann
>
> On Fri, Jul 16, 2021
Hi Deepak,
I added you as a contributor on the JIRA project.
Thanks,
Pierre
Le jeu. 8 juil. 2021 à 21:25, Deepak Kumar a écrit :
> Hi,
> I would like to have JIRA contributor's access. My JIRA username is dkrypt.
>
> I would like to contribute to MiNiFi and NiFi.
>
> Thank you,
> dkrypt
>
(only keeping dev list)
Hi Floriane,
I added you as a contributor on the NiFi JIRA project.
In order to open pull requests against the NiFi github project, you need to
fork the project, create branches on your fork with your code changes and
submit a pull request against the main branch of NiFi.
Congrats Marton!
Le ven. 25 juin 2021 à 01:56, Tony Kurc a écrit :
> congratulations!
>
> On Thu, Jun 24, 2021 at 6:23 PM Joe Witt wrote:
>
> > Congrats and thanks Marton
> >
> > On Thu, Jun 24, 2021 at 3:10 PM Otto Fowler
> > wrote:
> >
> > > Congratulations!
> > >
> > >
> > >
> > >
> > > Fro
Congrats!
Le ven. 25 juin 2021 à 00:23, Joe Witt a écrit :
> Well done Denes!
>
> On Thu, Jun 24, 2021 at 3:09 PM Otto Fowler
> wrote:
>
> > Congratulations!
> >
> >
> >
> >
> > From: Arpad Boda
> > Reply: dev@nifi.apache.org
> > Date: June 24, 2021 at 15:01:09
> > To: NiFi Developers List
I don't think we have but, just in case, all of the NiFi documentation is
also available directly from the NiFi UI using the top-right hamburger menu
and going into Help.
Pierre
Le mar. 15 juin 2021 à 20:05, Ioli, Bret P CIV USARMY SEC (USA)
a écrit :
> Good afternoon Apache NiFi Team,
>
>
>
>
Hi,
I think what you're looking is:
https://issues.apache.org/jira/browse/NIFI-8385
https://github.com/apache/nifi/pull/4952
This way when a bulletin is generated "because of" a flow file, the flow
file UUID would be part of the bulletin payload.
It'd mean that in addition to your external ID, s
Congrats Chris, your work is really appreciated and thanks a lot for the
last PR around AWS Kinesis!
Le jeu. 13 mai 2021 à 22:58, Otto Fowler a écrit :
> Awesome! Congratulations!
>
> > On May 13, 2021, at 16:25, Joe Witt wrote:
> >
> > On behalf of the Apache NiFI PMC, I am very pleased to an
I guess we could have a better error message but to me it sounds like there
is a field in your incoming JSON that contains
"hKaT0ytUPfgwNcjhDDtKRin42743t" and the name of this field is matching a
column in the Postgres table that is expecting a boolean. That's why the
casting does not work.
Can yo
Hi Philip,
I'd definitely see a lot of use cases for the first one. I'd however
provide an option to either have one request per record, or have a single
HTTP call to send the complete set of records to the endpoint.
I don't have a use case for the second one, but if you have one, that's
great and
+1 binding
Confirmed the main fix with a flow provided in the JIRA.
Thanks,
Pierre
Le jeu. 18 mars 2021 à 21:37, Mark Payne a écrit :
> +1 (binding)
>
> Was able to build, and successfully run all system tests, including those
> added for NIFI-8337. Also started up and manually verified that N
+1 (binding)
Went through the usual steps, checked a set of flows with a secured cluster
and a secured NiFi Registry.
Thanks Joe for taking care of this!
Pierre
Le sam. 13 mars 2021 à 06:34, M Tien a écrit :
> +1 (non-binding)
>
> Went through the release helper
> Verified a successful build
Hi Andrea,
You can now assign the JIRA to yourself, thanks for contributing to Apache
NiFi.
Pierre
Le ven. 12 mars 2021 à 13:12, Andrea Castello a
écrit :
> Hello,
>
> on March 12th I opened an issue for contributing a new processor (
> https://issues.apache.org/jira/browse/NIFI-8290) and I
Done. Thanks for your interest in NiFi.
Pierre
Le jeu. 4 mars 2021 à 11:44, Noble Numbat a
écrit :
> Can I please have contributor access to Jira. My username is
> noblenumbat360.
>
+1 binding
Went through the usual steps, built on CentOS, and tried a simple flow with
InvokeHTTP.
Thanks to everyone involved in this release!
Pierre
Le ven. 26 févr. 2021 à 06:54, Kevin Doran a écrit :
> +1 (binding)
>
> Ran through the release helper guide on Ubuntu.
>
> Nice work everyone!
+1 binding
Verified checksums and signature.
Built on Ubuntu 20.04.
Tested GenerateFlowFile -> MergeContent -> InvokeHTTP
Thanks,
Pierre
Le mer. 17 févr. 2021 à 14:24, Gábor Gyimesi a écrit :
> +1 (non-binding)
>
> Verified checksums and signature.
> Built on Ubuntu 20.04 with Kafka, Coap, SFT
he.org ;
> pierre.villard...@gmail.com
> *Cc:* Poddar, Rakesh Kumar ; Bhattacharjee,
> Koushik
> *Subject:* RE: Connectivity issue (Nifi to postgres)
>
>
> Hello Pierre,
>
> Logs has been attached for same.
>
>
>
> Regards
>
> Meghna Arora
>
>
+1 binding
Went through the usual verification process. Deployed secured cluster on
Google Cloud and checked integration with the NiFi Registry.
Thanks,
Pierre
Le dim. 14 févr. 2021 à 04:45, Peter Turcsanyi a
écrit :
> +1 non-binding
>
> Went through the release helper guide.
> Verified full b
Hi Chandan,
Note that your picture didn't come through your email. Please add it to an
external location and give a link to it.
Also, this processor is not a processor that is distributed via the Apache
NiFi project, I'd recommend reaching out to the authors/creators of this
processor.
Thanks,
Pi
Hi,
We'll need more information like the error message, stack trace, versions
you're using for NiFi / Registry / Postgres, configuration, etc.
Pierre
Le ven. 29 janv. 2021 à 16:48, Arora, Meghna a
écrit :
> Hello Team,
> We are facing some issue in NIFI connection.
>
>
> JDBC Driver of postgre
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 thi
Thanks Marton, I think it all makes sense!
Le mar. 26 janv. 2021 à 18:54, Marton Szasz a écrit :
> I moved the issues to 0.9.0 and Arpad removed 0.8.0 from Jira.
>
> Judging from the lack of replies, there seem to be no blocking issues.
> I volunteer to take RM duties for the release.
>
> Marton
f the
> graph
> >> bundle will be broken without it.
> >>
> >>>> On Tue, Jan 5, 2021, 11:50 Mark Bean wrote:
> >>>
> >>> I'd like to see this PR completed as well
> >>> https://github.com/apache/nifi/pull/4225
>
Hi Jon,
>From a monitoring perspective, I think it makes a lot of sense. This could
also help quickly finding in a large flow where the flow files may spend
most of the time (even though this could be seen via the lineage data as
well).
Thanks for filing the JIRA!
Pierre
Le ven. 8 janv. 2021 à
.
> > > > >
> > > > > On Thu, Nov 26, 2020 at 11:08 AM Mike Thomsen <
> mikerthom...@gmail.com>
> > > > > wrote:
> > > > > >
> > > > > > https://github.com/apache/nifi/pull/4638 - This is a big
> increase in
&g
Hi Eric,
I added you to the contributors for the project.
Thanks,
Pierre
Le lun. 21 déc. 2020 à 21:42, Eric Secules a écrit :
> Hello,
>
> Could you please grant contributor access to me (esecules)?
>
> Thanks,
> Eric
>
Hi Ivan,
I added you to the project. Looking forward to checking your contributions.
Thanks,
Pierre
Le lun. 21 déc. 2020 à 19:01, Ivan Kepes a écrit :
> Hello,
>
> Could someone please "Kepes" jira contributor access. I would like to
> work on: https://issues.apache.org/jira/browse/NIFI-8104
>
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 w
Hi Tim,
I added you as a contributor.
Thanks,
Pierre
Le mar. 17 nov. 2020 à 21:20, Smith, Tim a écrit :
> I thought I had done this awhile back but could you please add me to
> Apache NiFi Jira. I need to assign tickets to myself. My user name is:
> tlsmith
>
>
>
> Thanks
>
>
> Tim Smith
>
+1 to all of this - I'm really looking forward to seeing more of this!
Le lun. 16 nov. 2020 à 18:39, Kevin Doran a écrit :
> Thanks for your attention and effort on this, Matt. I look forward to the
> discuss threads, but at a high level, this sounds like a good and important
> step for MiNiFi J
ti...@datastax.com | datastax.com
>
> > On Nov 12, 2020, at 1:49 PM, Pierre Villard
> wrote:
> >
> > Hey Chris,
> >
> > I just added you, thanks!
> >
> > Pierre
> >
> > Le jeu. 12 nov. 2020 à 19:29, Chris Sampson
> > a écrit :
> &g
Hey Chris,
I just added you, thanks!
Pierre
Le jeu. 12 nov. 2020 à 19:29, Chris Sampson
a écrit :
> Please grant me Jira contributor access, username: Chris S
>
>
> Cheers,
>
> Chris Sampson
>
Hi,
I added you as a contributor on the JIRA project. Looking forward to seeing
your contributions.
Thanks,
Pierre
Le jeu. 12 nov. 2020 à 13:41, 李信穎 a écrit :
> Hello
>
> I want to try to contribute code to NiFi
> My Jira username is s9514171
>
> Thanks
>
Hi Alyssa,
You are now part of the contributors on the JIRA project.
Looking forward to seeing your contributions.
Thanks,
Pierre
Le jeu. 5 nov. 2020 à 07:42, Alyssa Romanos a
écrit :
> Hi there,
>
> I'd like to have Jira contributor access to the Apache Nifi board. My Jira
> username is aroma
Hello
The Apache NiFi team would like to announce the release of Apache NiFi
Registry 0.8.0.
Apache NiFi is an easy to use, powerful, and reliable system to process and
distribute data. Apache NiFi was made for dataflow. It supports highly
configurable directed graphs of data routing, transforma
Apache NiFi Community,
I am pleased to announce that the nifi-registry-0.8.0 release of Apache
NiFi Registry passes with:
4 +1 (binding) votes
1 +1 (non-binding) votes
0 0 votes
0 -1 votes
Thanks to all who helped make this release possible.
Here is the PMC vote thread:
https://m
ina 10.15.2)
> > -Tested secure NiFi Registry 0.8.0 with secure NiFi 1.12.1
> > -Tested basic flow, bucket and user functionality
> > -Tested common versioned flow use cases
> > -Reviewed documentation updates
> >
> > Drew
> >
> > > On Oct 14, 2020
Hello,
I am pleased to be calling this vote for the source release of Apache NiFi
Registry 0.8.0.
The source zip, including signatures, digests, etc. can be found at:
https://repository.apache.org/content/repositories/orgapachenifi-1174
The source being voted upon and the convenience binaries ca
Thanks Bryan! Happy to give the RM process a try for this 0.8.0 release.
Le mar. 13 oct. 2020 à 16:37, Joe Witt a écrit :
> sounds good and thanks. happy to rm a nifi release too if needed.
>
> On Tue, Oct 13, 2020 at 7:33 AM Bryan Bende wrote:
>
> > Would like to kick out registry 0.8.0 soon.
Nissim,
Thanks a lot for your contribution but there are 277 pull requests opened
at this time. This is a community effort, and if you expect people to
review your PRs, you'd have to also try reviewing PRs opened by others in
the community. Otherwise this will need to wait for someone with some
ba
+1 (binding)
Went through usual verification steps.
Thanks Joe for RM'ing!
Le ven. 25 sept. 2020 à 13:30, Tony Kurc a écrit :
> +1 (binding)
>
> Verified signature and hashes. Built without issue on ubuntu 18.04 x86_64
> with openjdk11. Saw no issues with LICENSE or NOTICE.
>
> Tony
>
> On Wed,
t sort of I/O is not biting me. The process itself is highly
> ‘parallelisable’ but I can’t get NiFi to use more than about 10% of the CPU
> load. This is the only purpose this machine has - I want it to work much
> harder!
>
> On Fri, 18 Sep 2020 at 20:56, Pierre Vi
+1 (binding) Release this package as nifi-nar-maven-plugin-1.3.2
Checked commit and hashes, looks good. Thanks Bryan!
Le mer. 16 sept. 2020 à 19:10, Matt Burgess a écrit :
> +1 (binding) Release this package as nifi-nar-maven-plugin-1.3.2
>
> Verified Git commit and hashes, ran full NiFi build
Hi,
Do you have backpressure with flow files accumulating somewhere in your
flow? If not, then you probably don't need more threads.
If you do find bottlenecks in your flow design, then you can look at
increasing the concurrent tasks on specific processors to have
multi-threading. Note that it's n
+1 as well!
Thanks Bryan!
Le mer. 16 sept. 2020 à 18:22, Joe Witt a écrit :
> For sure. Lets roll
>
> thanks
>
> On Wed, Sep 16, 2020 at 9:17 AM Kevin Doran wrote:
>
> > +1 Thanks for fixing and RM’ing, Bryan!
> >
> >
> >
> > > On Sep 16, 2020, at 11:48, Matt Burgess wrote:
> >
> > >
> >
> >
Hi Dominik,
I added you to the contributors on the NiFi JIRA project. Looking forward
to contributing with you.
Thanks,
Pierre
Le dim. 13 sept. 2020 à 23:17, Dominik H a écrit :
> Hi
>
> I would liike to contribute to nifi project, my jira username is doodzio.
>
> Best regards
> Dominik
>
+1 binding
I deployed a secured cluster on GCP using my terraform scripts (with ZK
3.5.8) and I confirmed the SAN issue was addressed.
Updated: https://github.com/pvillard31/nifi-gcp-terraform
Le mar. 8 sept. 2020 à 19:00, Joe Witt a écrit :
> Hello,
>
> I am pleased to be calling this vote for
Hi Gavin,
Can you rebase and squash your commits into one single commit for your pull
request? (you may want to do it after 1.12.0 is released, which should
happen today or tomorrow so that you can update the reference to
1.13.0-SNAPSHOT)
Then there are a few things that should be changed: the pr
+1 (binding)
Went through the usual steps. Deployed a secured cluster on GCP and tried a
few flows. Confirmed some fixes, tested the ScriptedTransformRecord
processor, and the new flowfile concurrency features.
Thanks all for this great release, a lot of really good stuff!
Thanks Joe for taking c
Yeah this is definitely one of the awesome new features coming with 1.12!
Le mer. 5 août 2020 à 19:59, Mike Thomsen a écrit :
> I got a chance to use it on a particularly nasty data set my client
> has that has a lot of fairly deep intervention with LookupRecord and
> custom services (ie it's cl
Hi Chad,
I know Matthew Burgess is actively working on bringing back MiNiFi Java
into NiFi and providing a way of running NiFi in a "headless mode" which
would be the same as running MiNiFi Java. A large part of this effort has
been merged recently [1]. He might be able to provide more details abo
Congratulations Marton! Well deserved!
Le lun. 3 août 2020 à 10:25, Peter Turcsanyi a
écrit :
> Congrats Marton!
>
> On Mon, Aug 3, 2020 at 10:02 AM Arpad Boda wrote:
>
> > Apache NiFi community,
> >
> > On behalf of the Apache NiFI PMC, I am very pleased to announce that
> Marton
> > has accep
Hi Mahieddine,
I added you as a contributor on the JIRA. Looking forward to seeing your
contributions!
Welcome to the Apache NiFi community.
Pierre
Le ven. 31 juil. 2020 à 20:23, mahieddine cherif
a écrit :
> Hi,
>
> I want to contribute to the Apache NiFi project with some nice stuff and
> wo
Hi Kent,
I added you as a contributor on the JIRA project. You should be able to
assign the JIRAs to yourself.
Thanks for your contributions and your involvement in this community!
Pierre
Le mer. 29 juil. 2020 à 07:22, Khuê Nguyễn Trần Tú
a écrit :
> Hello,
>
> I would like to request access t
+1 (binding)
* went through the usual release verification steps (signatures, build,
contrib check, licenses)
* deployed a local NR 0.7.0 instance with a single local NiFi
1.12.0-SNAPSHOT (non secure)
Thanks Bryan for taking care of this!
Le ven. 17 juil. 2020 à 17:46, Matt Burgess a écrit :
>
g progress on the OIDC support,
> > so I will wait a little bit to see if we can get that in, but if it
> starts
> > taking longer then I'll proceed with getting an RC out.
> >
> > On Mon, Jul 6, 2020 at 5:41 AM Pierre Villard <
> pierre.villard...@gmail.com&
Regarding the NiFi Registry 0.7.0 release - if we can have the OIDC support
in it, that would be great. I know Nathan is working on it (based on the
JIRA) not sure if this is something close to being ready.
Le sam. 4 juil. 2020 à 21:15, Mike Thomsen a
écrit :
> FYI, if we add in https://github.c
Great report, thanks for taking care of it Joe!
Le mer. 1 juil. 2020 à 16:57, Joe Witt a écrit :
> Team,
>
> Here is the board report I've submitted for the July meeting.
>
> Thanks as always for the great progress!
>
>
> ## Description:
> The mission of NiFi is the creation and maintenance of s
Hi Jason,
I'd recommended filing a JIRA here [1].
The more detailed the description is, the better.
Then you can submit a change through a Pull Request on Github. You might
want to have a look at the contributor guide [2].
Let me know if you have any questions.
[1] https://issues.apache.org/jir
> In my perspective this should be an issue for the entire community. Being
> able to identify an issue that directly affects another person but not
> one’s self is the definition of privilege. If I can look at how the use of
> these words in someone’s daily life or career impacts them negatively,
I can't say how much we will miss you Jeff. You were a great guy, always
nice and helpful with everyone. You always went the extra mile to make
things easier and more robust.
RIP Jeff
Le lun. 15 juin 2020 à 21:13, Jeremy Dyer a écrit :
> This is shocking and heartbreaking news. Jeff was a great
Hi,
That's really good feedback and I'm also doing similar things with my own
k8s/contained based deployments. Let's try to see if there are low-hanging
fruits that could be easily added in NiFi. Happy to look at / review pull
requests if there are things you'd like to see upstream.
Thanks,
Pierr
Awesome Drew! Congrats! Your work is super useful for all the community,
well deserved!
Le ven. 29 mai 2020 à 21:55, Tony Kurc a écrit :
> NiFi Community,
>
> On behalf of the Apache NiFi PMC, I am pleased to announce that Drew Lim
> has accepted the PMC's invitation to join the Apache NiFi PMC.
Congrats Arpad, very well deserved!
Le ven. 29 mai 2020 à 21:48, Tony Kurc a écrit :
> NiFi Community,
>
> On behalf of the Apache NiFi PMC, I am pleased to announce that Arpad Boda
> has accepted the PMC's invitation to join the Apache NiFi PMC.
>
> In addition to being a regular code contribut
Hi,
Can you make sure the host where NiFi is running has its time correctly
sync'ed (with systems like TLSdate or NTP)?
Sounds like there is a time difference between the NiFi host server and the
server issuing the token.
Thanks,
Pierre
Le ven. 29 mai 2020 à 18:54, Ashutosh Kumar (Group)
a écri
Hi,
I added you as a contributor to the NIFI project, you should be able to
assign JIRAs to yourself going forward. Let me know if that is not the case.
Welcome in the Apache NiFi community and looking forward to helping with
your contributions.
Thanks,
Pierre
Le lun. 25 mai 2020 à 10:27, 酷酷的诚
Anuj,
We don't make releases for previous release lines of Apache NiFi (besides
1.9.2 is more than one year old). There is an ongoing discussion for
releasing either a 1.11.5 version or a 1.12.0 version. Assuming the pull
request is reviewed and merged before we make this release, then it'd
availa
101 - 200 of 540 matches
Mail list logo
