Re: [discuss] removal of nifi-external module in 2.x/deprecate in 1.x

I would say nuke it, as you are saying. I would also say you should cross post this to users@ as they will have relevant input On May 7, 2024 at 1:32:11 PM, Joe Witt (joew...@apache.org) wrote: Team, The only component remaining is kafka-connect in the nifi-external module. As noted in [1] it

Re: [VOTE] Release Apache NiFi 2.0.0-M1 (RC1)

+1 (non-binding) Validated hashes, signatures, build from source, and test run. ❯ mvn --version Apache Maven 3.9.5 (57804ffe001d7215b5e7bcb531cf83df38f93546) Maven home: /opt/homebrew/Cellar/maven/3.9.5/libexec Java version: 21.0.1, vendor: Eclipse Adoptium, runtime:

Re: [DISCUSS] Release Timing for NiFi 2.0.0 M1 and 1.24.0

:15:18 AM, Otto Fowler (ottobackwa...@gmail.com) wrote: ~/t/nifi-release-2/nifi-/nifi-as/target/nifi-2.0.0-M1-bin/nifi-2.0.0-M1/logs ─── at 09:13:24 ❯ grep Generated nifi-app.log ~/t/nifi-release-2/nifi-/nifi-as/target/nifi-2.0.0-M1-bin/nifi-2.0.0-M1/logs ─── at 09:13:27

Re: [DISCUSS] Release Timing for NiFi 2.0.0 M1 and 1.24.0

( exceptionfact...@apache.org) wrote: Otto, Can you provide the exact command you are running? Running the following command from the NiFi home directory should work on a new installation: grep Generated logs/nifi-app.log Regards, David Handermann On Tue, Nov 14, 2023 at 7:57 AM Otto Fowler wrote

Re: [DISCUSS] Release Timing for NiFi 2.0.0 M1 and 1.24.0

I”m trying to verify the 2.0.0-M1 release and it is not generating the default user and password per the README ( ie. The grep fails and I cannot find them ). Am I missing something? ❯ mvn --version Apache Maven 3.9.5 (57804ffe001d7215b5e7bcb531cf83df38f93546) Maven home:

Re: Custom-processor configuration suggestions

``` ┌──┐ │ │ │ processor instance │┐ │ ││ └──┘│ .─. │

Re: [VOTE] Release Apache NiFi 1.23.0 (RC2)

t;mac os x", version: "13.4.1", arch: "aarch64", family: "mac" On July 21, 2023 at 8:05:49 PM, Otto Fowler (ottobackwa...@gmail.com) wrote: +1 (non-binding) On July 20, 2023 at 8:16:12 PM, David Handermann ( exceptionfact...@apache.org) wrote: Tea

Re: [VOTE] Release Apache NiFi 1.23.0 (RC2)

+1 (non-binding) On July 20, 2023 at 8:16:12 PM, David Handermann ( exceptionfact...@apache.org) wrote: Team, I am pleased to be calling this vote for the source release of Apache NiFi 1.23.0. The source zip, including signatures, digests, etc. can be found at:

Re: [VOTE] Release Apache NiFi 1.23.0 (RC1)

+1 Ran through verification and ran app. ``` Apache Maven 3.9.3 (21122926829f1ead511c958d89bd2f672198ae9f) Maven home: /opt/homebrew/Cellar/maven/3.9.3/libexec Java version: 11.0.18, vendor: Eclipse Adoptium, runtime: /Library/Java/JavaVirtualMachines/temurin-11.jdk/Contents/Home Default

Re: [ANNOUNCE] New nifi PMC Member Nandor Soma Abonyi

Congratulations! On June 26, 2023 at 7:11:16 PM, Joe Witt (joe.w...@gmail.com) wrote: On behalf of the Apache NiFI PMC, I am very pleased to announce that Nandor has accepted the PMC's invitation to join the Apache NiFi PMC. We greatly appreciate the PR reviews and code contributions and

Re: Implementation question: PLC4X integration - Subscription operation

) would require around 3 more standard processors so I don't see a big difference. Unai On 2023/05/17 15:32:24 Otto Fowler wrote: Hi Unai! Would this be a single thread, just listening? Is this pure exception based processing ( where you only listen for things ) or is it possible to have

Re: Implementation question: PLC4X integration - Subscription operation

Hi Unai! Would this be a single thread, just listening? Is this pure exception based processing ( where you only listen for things ) or is it possible to have to simulate this by polling some of the endpoints? On May 17, 2023 at 10:28:24 AM, Unai Leria (unai.le...@zylk.net.invalid) wrote: Hi

Re: [discuss] NiFi 1.20 and NiFi 2.0

br/>>>>>>>>>> br/>>>>>>>>>> br/>>>>>>>>>> Would the community benefit from one or more milestone releases of >>>>>>>>> 2.0, >>>>>>>> to >>>>>>&

Re: [discuss] NiFi 1.20 and NiFi 2.0

if we were bringing fixes from main (1.20.0-SNAPSHOT) back to a maintenance line like (1.19.x). For precedent, we followed this same approach going from the 0.x line to 1.0.0 and there wasn't any major issue. On Tue, Jan 10, 2023 at 7:07 AM Otto Fowler wrote: > It was also mentioned in anot

Re: [discuss] NiFi 1.20 and NiFi 2.0

It was also mentioned in another thread that we need to have agreement on our explicit strategy and support for 1.x going forward, did that happen? From: Otto Fowler Reply: Otto Fowler Date: January 10, 2023 at 07:02:34 To: dev@nifi.apache.org Subject: Re: [discuss] NiFi 1.20 and NiFi 2.0

Re: [discuss] NiFi 1.20 and NiFi 2.0

There needs to be an update to the contributing guide as to how to submit PRs to 1.x or 2.x etc. From: Joe Witt Reply: dev@nifi.apache.org Date: January 9, 2023 at 15:53:16 To: dev@nifi.apache.org Subject: [discuss] NiFi 1.20 and NiFi 2.0 Team, As David mentioned in [1] following a

Re: [DISCUSS] Finalizing Release Goals for NiFi 2.0

Sorry to be late to this, the goals seem great. The question that comes to my mind is will the current 1.x line will be maintained? That may be a parallel issue to the goals, but it is important if we are dropping support for Java versions. I would think that *some* position on that has to be

Re: [VOTE] Release Apache NiFi 1.18.0 (RC3)

+1 ( non-binding) ran through release steps Apache Maven 3.8.6 (84538c9988a25aec085021c365c560670ad80f63) Maven home: /usr/local/Cellar/maven/3.8.6/libexec Java version: 1.8.0_292, vendor: AdoptOpenJDK, runtime: /Library/Java/JavaVirtualMachines/adoptopenjdk-8.jdk/Contents/Home/jre Default

Re: [discuss] Apache NiFi 1.18 release candidate

I am having issues building right at the start: [ERROR] [ERROR] Some problems were encountered while processing the POMs: [FATAL] Non-resolvable parent POM for org.apache.nifi:nifi-ranger-bundle:1.18.0-SNAPSHOT: Could not find artifact org.apache.nifi:nifi-nar-bundles:pom:1.18.0-SNAPSHOT and

Re: New NiFi PMC Member Nathan Gough

Congratulations, thanks for all you do From: David Handermann Reply: dev@nifi.apache.org Date: September 7, 2022 at 12:10:21 To: dev@nifi.apache.org Subject: New NiFi PMC Member Nathan Gough Apache NiFi Community, On behalf of the Apache NiFi Project Management Committee, I am very

Re: [VOTE] Release Apache NiFi 1.17.0 (rc1)

+1 (non-binding) Followed release helper Apache Maven 3.8.6 (84538c9988a25aec085021c365c560670ad80f63) Maven home: /usr/local/Cellar/maven/3.8.6/libexec Java version: 1.8.0_292, vendor: AdoptOpenJDK, runtime: /Library/Java/JavaVirtualMachines/adoptopenjdk-8.jdk/Contents/Home/jre Default locale:

Re: How to manage security artifacts from a custom processor

Usually, you would write you custom processor to support the StandardSSLSocketService: https://nifi.apache.org/docs/nifi-docs/components/org.apache.nifi/nifi-ssl-context-service-nar/1.16.3/org.apache.nifi.ssl.StandardSSLContextService/index.html From: Russell Bateman Reply:

Re: Missing maven dependencies when building nifi

What country are you in? Are you under export controls? From: Phil H Reply: dev@nifi.apache.org Date: April 6, 2022 at 07:08:45 To: dev@nifi.apache.org Subject: Re: Missing maven dependencies when building nifi So, I restarted the whole process inside a CentOS VM. The only way I could

Re: [ANNOUNCE] New Apache NiFi Committer Adam Markovics

Congratulations! From: Marton Szasz Reply: dev@nifi.apache.org Date: March 25, 2022 at 08:50:07 To: dev@nifi.apache.org Subject: [ANNOUNCE] New Apache NiFi Committer Adam Markovics Apache NiFi community, On behalf of the Apache NiFi PMC, I am very pleased to announce that Adam Markovics

Re: SplitContent doesn’t support regex?

Joe, I don’t know if we can make the case for a stand alone processor for doing this on top of that, if so, I’d be willing to take a look at that. From: Otto Fowler Reply: Otto Fowler Date: March 19, 2022 at 13:40:07 To: dev@nifi.apache.org , Phil H Subject:  Re: SplitContent doesn’t

Re: SplitContent doesn’t support regex?

In the Apache Metron Project (in the attic now) we used https://github.com/nishihatapalmer/byteseek to do pcap searches, maybe you can check that out. From: Phil H Reply: dev@nifi.apache.org Date: March 16, 2022 at 20:04:58 To: dev@nifi.apache.org Subject: Re: SplitContent doesn’t

Re: [ANNOUNCE] New Apache NiFi Committer Paul Grey

Congratulations! From: David Handermann Reply: dev@nifi.apache.org Date: March 16, 2022 at 18:46:09 To: dev@nifi.apache.org Subject: [ANNOUNCE] New Apache NiFi Committer Paul Grey Apache NiFi community, On behalf of the Apache NiFi PMC, I am very pleased to announce that Paul Grey has

Re: [VOTE] Release Apache NiFi 1.15.3 (rc1)

+1 ( non-binding ) built and tested with java 11.0.12 followed release guide From: Joe Witt Reply: dev@nifi.apache.org Date: January 13, 2022 at 15:44:42 To: dev@nifi.apache.org Subject: [VOTE] Release Apache NiFi 1.15.3 (rc1) Hello, I am pleased to be calling this vote for the source

Re: [DISCUSS] Release Apache NiFi 1.15.3 (rc1)

recent Java 11 and see if results differ. Thanks On Fri, Jan 14, 2022 at 9:10 AM Otto Fowler wrote: > > I am seeing errors building the release candidate with failed tests. Does > anyone have any insight into these failures? > >

[DISCUSS] Release Apache NiFi 1.15.3 (rc1)

I am seeing errors building the release candidate with failed tests. Does anyone have any insight into these failures? INFO] [INFO] --- [INFO] T E S T S [INFO] --- [ERROR] WARNING: An illegal

Re: [VOTE] Release Apache NiFi NAR Maven Plugin 1.3.3

+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.3 Hello, I am pleased to be calling this vote for the source release of Apache

Re: [DISCUSS] Docs from non packaged NARs

This makes me wonder how documentation is going to work with the registry, should the documentation show all the nars that are in the registry and available or all the cars local? etc. From: Pierre Villard Reply: dev@nifi.apache.org Date: November 9, 2021 at 18:17:30 To: dev@nifi.apache.org

Re: [VOTE] Release Apache NiFi 1.15.0 (rc3)

+1 Ran through verification, build and run From: Joe Witt Reply: dev@nifi.apache.org Date: November 3, 2021 at 15:29:41 To: dev@nifi.apache.org Subject: [VOTE] Release Apache NiFi 1.15.0 (rc3) Hello, I am pleased to be calling this vote for the source release of Apache NiFi 1.15.0. The

Re: [VOTE] Release Apache NiFi 1.15.0

+1 Checked all the sources, hashes etc Built and ran From: Joe Witt Reply: dev@nifi.apache.org Date: November 1, 2021 at 20:18:04 To: dev@nifi.apache.org Subject: [VOTE] Release Apache NiFi 1.15.0 Hello, I am pleased to be calling this vote for the source release of Apache NiFi 1.15.0.

Re: [discuss] NiFi 1.15

This release, we are verifying not only Nifi, but also Minifi Java. At least that is my understanding. This would be my first time having *anything* to do with minifi, i’ve not even run it before. As such, I think the RC validation guide needs to be update to include the information about now

Re: [discuss] NiFi 1.15

Is there a discuss thread for the release? I only see the vote and I have a question about the verification. My mail must be messed up, i have this mail with no replies… then vote thread. From: Joe Witt Reply: dev@nifi.apache.org Date: October 25, 2021 at 11:59:39 To: dev@nifi.apache.org

Re: [ANNOUNCE] New NiFi PMC Member David Handermann

Congratulations! From: Bryan Bende Reply: dev@nifi.apache.org Date: September 17, 2021 at 08:56:43 To: dev@nifi.apache.org Subject: [ANNOUNCE] New NiFi PMC Member David Handermann NiFi Community, On behalf of the Apache NiFI PMC, I am very pleased to announce that David Handermann has

Re: Flood of JIRAs and presumably PRs to follow for junit-5 migration?

perhaps we can have a jira label and PR naming convention for things that fall under this as well, to set consistent expectations for review and work From: Kevin Doran Reply: dev@nifi.apache.org Date: August 31, 2021 at 18:06:48 To: dev@nifi.apache.org Subject: Re: Flood of JIRAs and

Re: Contributor

https://nifi.apache.org/docs/nifi-docs/html/developer-guide.html#how-to-contribute-to-apache-nifi From: Roberto Frederico Togo Santos Reply: dev@nifi.apache.org Date: August 20, 2021 at 21:04:20 To: dev@nifi.apache.org Subject: Contributor Hi. I have added in Oracle12DatabaseAdapter.java

Re: [DISCUSS] NiFi 2.0 Release Goals

:23:43 To: dev@nifi.apache.org Subject: Re: [DISCUSS] NiFi 2.0 Release Goals If I put Jira's in, then I'd have to admit I'm a developer vs a user :-) I'm just a power user at heart :-) ... Ryan On Thu, Aug 5, 2021 at 2:01 PM Otto Fowler wrote: > Ryan, these are awesome, are there ji

Re: [DISCUSS] NiFi 2.0 Release Goals

maintained to whatever the 2.0 API looks like, there's > > >> possibly > > >>> little harm keeping them around. > > >>> > > >>> And by the way, what happened to the "marketplace" concept? Is this > being > > >

Re: [DISCUSS] NiFi 2.0 Release Goals

e towards a mono-repo where everything is released > > > > > together. Eventually it would still be nice to have a smaller base > > > > > distribution containing just the framework and standard NARs, but it > > > > > is hard to tackle that until we prov

Re: [DISCUSS] NiFi 2.0 Release Goals

The issue with updating the aws sdk is if it breaks any one of the processors. the Web Gateway API invoke processor for example is not using a high level purpose build client and may break. If we change the aws version, we need to coordinate in such a way that they all can come along reasonably.

Re: [DISCUSS] NiFi Registry -> NiFi consensus

+1 (non-binding) From: Matt Burgess Reply: dev@nifi.apache.org Date: July 16, 2021 at 14:20:20 To: dev@nifi.apache.org Subject: [DISCUSS] NiFi Registry -> NiFi consensus All, We've been asked to record our consensus for the move of NiFi Registry to the NiFi codebase in a mailing list

Re: [discuss] nifi 1.14.0

PR up From: Otto Fowler Reply: Otto Fowler Date: July 12, 2021 at 20:20:30 To: dev@nifi.apache.org Subject: Re: [discuss] nifi 1.14.0 I’ll take care of it. I’ll make the minimum 3.6.0 From: Joe Witt Reply: dev@nifi.apache.org Date: July 12, 2021 at 18:25:28 To: dev@nifi.apache.org

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

+1 ( non binding ) Apache Maven 3.8.1 (05c21c65bdfed0f71a2f2ada8b84da59348c4c5d) Maven home: /usr/local/Cellar/maven/3.8.1/libexec Java version: 1.8.0_292, vendor: AdoptOpenJDK, runtime: /Library/Java/JavaVirtualMachines/adoptopenjdk-8.jdk/Contents/Home/jre Default locale: en_US, platform

Re: [discuss] nifi 1.14.0

requirements and such so we're probably really tight on required version at this point anyway. I'd not be sinking the RC for this. Just a good JIRA to work on. Thanks On Mon, Jul 12, 2021 at 12:59 PM Otto Fowler wrote: > > NIFI-8778 > > From: Otto Fowler > Reply: Otto Fowler > D

Re: [discuss] nifi 1.14.0

NIFI-8778 From: Otto Fowler Reply: Otto Fowler Date: July 12, 2021 at 13:56:36 To: dev@nifi.apache.org Subject: Re: [discuss] nifi 1.14.0 I see an issue, though I’m not sure if we want to cancel the RC so I’m asking before voting. The documentation states that we require Apache Maven

Re: [discuss] nifi 1.14.0

8220 > <https://issues.apache.org/jira/browse/NIFI-8220> would > be > great > to > have > completed. Most of the elements are in place, and the > current > Pull > Request > for NIFI-8516 <https://github.com/apache/nifi/pull/5068 > > is > under > review

Re: [ANNOUNCE] New NiFi PMC Member Marton Szasz

Congratulations! From: Arpad Boda Reply: dev@nifi.apache.org Date: June 24, 2021 at 15:01:31 To: NiFi Developers List Subject: [ANNOUNCE] New NiFi PMC Member Marton Szasz On behalf of the Apache NiFI PMC, I am very pleased to announce that Marton has accepted the PMC's invitation to

Re: [ANNOUNCE] New Apache NiFi Committer Denes Arvay

Congratulations! From: Arpad Boda Reply: dev@nifi.apache.org Date: June 24, 2021 at 15:01:09 To: NiFi Developers List Subject: [ANNOUNCE] New Apache NiFi Committer Denes Arvay On behalf of the Apache NiFI PMC, I am very pleased to announce that Denes has accepted the PMC's invitation

Re: [discuss] nifi 1.14.0

I think NIFI-8625 and NIFI-8461 need to be understood and addressed. > On May 27, 2021, at 13:29, Joe Witt wrote: > > Team, > > There has been a tremendous amount of work already on the 1.14 line as shown: > > https://issues.apache.org/jira/projects/NIFI/versions/12349644 > > These include

Re: [ANNOUNCE] New Apache NiFi Committer Chris Sampson

Awesome! Congratulations! > On May 13, 2021, at 16:25, Joe Witt wrote: > > On behalf of the Apache NiFI PMC, I am very pleased to announce that > Chris has accepted the PMC's invitation to become a committer on the > Apache NiFi project. We greatly appreciate the contributions from Chris > on

Re: MiNiFi Java -> NiFi

Awesome Job Matt! > On Apr 28, 2021, at 14:08, Matt Burgess wrote: > > All, > > Now that [1] is merged, MiNiFi Java is now officially in the NiFi > codebase! Thanks to all who participated in discussions, reviews, and > testing. Here are some notes on what this means going forward: > > - All

Apache Project issues with available GitHub Action resources across projects

As you can probably imagine, it takes a lot of resources in order to CI for all the Apache projects. Periodically this becomes an issue, as the donated resources from cloud CI providers ( Travis and now GitHub Actions ) end up queuing and delaying builds across Apache projects because of

Re: Stale PR automatic closure

> I'm not clear on what you mean. But here we're talking about our > communities usage of Github in particular as a convenient vehicle to > support contributions. The ASF/Git (gitbox) is a different animal. > > Thanks > > On Thu, Mar 25, 2021 at 12:02 PM Otto Fowler > wro

Re: Stale PR automatic closure

What would be nice is if this could be part of the ASF official .yml for git On Thu, Mar 25, 2021 at 2:42 PM Joe Witt wrote: > Team, > > We've discussed it in various forums but I want to formally move to > taking action on our PR situation. As of a couple hours ago we had > 280 or so open

Re: [ANNOUNCE] New NiFi PMC Member Joey Frazee

Congratulations! On Thu, Mar 25, 2021 at 2:54 PM Joe Witt wrote: > NiFi Community, > > On behalf of the Apache NiFi PMC, I am pleased to announce that Joey Frazee > has accepted the PMC's invitation to join the Apache NiFi PMC. > > Joey has been a contributor and committer of Apache NiFi for

Re: [EXT] [ANNOUNCE] New Apache NiFi Committer Otto Fowler

Witt > > Date: Monday, March 22, 2021 at 12:16 PM > > To: dev@nifi.apache.org > > Subject: [EXT] [ANNOUNCE] New Apache NiFi Committer Otto Fowler > > CAUTION: EXTERNAL EMAIL. Do not click links or open attachments unless > you > > recognize the sender and were exp

Re: [VOTE] Release Apache NiFi 1.13.2

+1 Apache Maven 3.6.3 (cecedd343002696d0abb50b32b541b8a6ba2883f) Maven home: /usr/local/Cellar/maven/3.6.3_1/libexec Java version: 1.8.0_282, vendor: AdoptOpenJDK, runtime: /Library/Java/JavaVirtualMachines/adoptopenjdk-8.jdk/Contents/Home/jre Default locale: en_US, platform encoding: UTF-8 OS

Re: [RESULT][VOTE] Release Apache NiFi 1.13.1

Awesome job, thanks Joe! > On Mar 15, 2021, at 11:11, Joe Witt wrote: > > Apache NiFi Community, > > I am pleased to announce that the 1.13.1 release of Apache NiFi passes with >8 +1 (binding) votes >8 +1 (non-binding) votes >0 0 votes >0 -1 votes > > Thanks to all who helped

Re: [VOTE] Release Apache NiFi 1.13.1

+1 Apache Maven 3.6.3 (cecedd343002696d0abb50b32b541b8a6ba2883f) Maven home: /usr/local/Cellar/maven/3.6.3_1/libexec Java version: 1.8.0_282, vendor: AdoptOpenJDK, runtime: /Library/Java/JavaVirtualMachines/adoptopenjdk-8.jdk/Contents/Home/jre Default locale: en_US, platform encoding: UTF-8 OS

Re: [RESULT][VOTE] Release Apache NiFi 1.13.0

Great job everyone, thanks Joe! > On Feb 15, 2021, at 11:48, Joe Witt wrote: > > Apache NiFi Community, > > I am pleased to announce that the 1.13.0 release of Apache NiFi passes with >6 +1 (binding) votes >7 +1 (non-binding) votes >0 0 votes >0 -1 votes > > Thanks to all who

Re: [VOTE] Release Apache NiFi 1.13.0 (rc4)

+1 Apache Maven 3.6.3 (cecedd343002696d0abb50b32b541b8a6ba2883f) Maven home: /usr/local/Cellar/maven/3.6.3_1/libexec Java version: 1.8.0_282, vendor: AdoptOpenJDK, runtime: /Library/Java/JavaVirtualMachines/adoptopenjdk-8.jdk/Contents/Home/jre Default locale: en_US, platform encoding: UTF-8 OS

Re: [discuss] we need to enable secure by default...

Aren’t most of these applications installed by an installer? Maybe we can have one or more installers that setup a secure instance, and those installers could be the *production* nifi, and keep the zip distribution open for developers? > On Feb 10, 2021, at 10:04, David Handermann > wrote: >

Re: [VOTE] Release Apache NiFi 1.13.0 (rc3)

+1 Apache Maven 3.6.3 (cecedd343002696d0abb50b32b541b8a6ba2883f) Maven home: /usr/local/Cellar/maven/3.6.3_1/libexec Java version: 1.8.0_282, vendor: AdoptOpenJDK, runtime: /Library/Java/JavaVirtualMachines/adoptopenjdk-8.jdk/Contents/Home/jre Default locale: en_US, platform encoding: UTF-8 OS

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

+1 Apache Maven 3.6.3 (cecedd343002696d0abb50b32b541b8a6ba2883f) Maven home: /usr/local/Cellar/maven/3.6.3_1/libexec Java version: 1.8.0_282, vendor: AdoptOpenJDK, runtime: /Library/Java/JavaVirtualMachines/adoptopenjdk-8.jdk/Contents/Home/jre Default locale: en_US, platform encoding: UTF-8 OS

Re: [VOTE] Release Apache NiFi 1.13.0

+1 Followed the guide, built and ran, verified some of the new processor documentation. Note: was able to get this to build with : Maven home: /usr/local/Cellar/maven/3.6.3_1/libexec Java version: 1.8.0_282, vendor: AdoptOpenJDK, runtime:

Re: [DISCUSS] Release of Apache NiFi 1.13.0

Although I _have_ been building with this jdk for a long time, I may not have built with it since the TLS changes when it. Maybe that is a factor. > On Jan 28, 2021, at 10:15, Otto Fowler wrote: > > Thanks Joe, > > I’m started down that road right after I sent this. I’ll upd

Re: [DISCUSS] Release of Apache NiFi 1.13.0

ote: > > 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, Ja

Re: [DISCUSS] Release of Apache NiFi 1.13.0

t;> 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 >>>>>>

Re: Question about ListenTCP processor

It is in the base class https://github.com/apache/nifi/blob/aa741cc5967f62c3c38c2a47e712b7faa6fe19ff/nifi-nar-bundles/nifi-extension-utils/nifi-processor-utils/src/main/java/org/apache/nifi/processor/util/listen/AbstractListenEventBatchingProcessor.java#L50 > On Jan 26, 2021, at 21:31, Hodor,

Re: [DISCUSS] Release of Apache NiFi 1.13.0

I would still like to get https://github.com/apache/nifi/pull/4384 in and not miss the release. > On Jan 12, 2021, at 13:17, Pierre Villard wrote: > > Hi all, > > Current status about what we want to get in based on this thread: > - NIFI-8034 -

Re: Static processor design

*ListenDynamicPropertyChange > On Jan 8, 2021, at 12:42, Otto Fowler wrote: > > So you would be implementing ListDynamicPropertyChange kind of. > > >> On Jan 8, 2021, at 12:41, Otto Fowler > <mailto:ottobackwa...@gmail.com>> wrote: >> >> What a

Re: Static processor design

So you would be implementing ListDynamicPropertyChange kind of. > On Jan 8, 2021, at 12:41, Otto Fowler wrote: > > What are the attributes of the processor? > Do you have : > > @InputRequirement(InputRequirement.Requirement.INPUT_FORBIDDEN) > or anything? >

Re: Static processor design

What are the attributes of the processor? Do you have : @InputRequirement(InputRequirement.Requirement.INPUT_FORBIDDEN) or anything? You should take a look at the Listen** processors. They do not have any inputs etc, and run processing queued input from a background thread. You can have on

Re: Using record data with the graph bundle

It is awesome that you guys are contributing all this awesome graph functionality, thanks Mike and colleagues! From: Mike Thomsen Reply: dev@nifi.apache.org Date: December 1, 2020 at 13:25:46 To: dev@nifi.apache.org Subject: Using record data with the graph bundle I just approved and

Re: [DISCUSS] Release of Apache NiFi 1.13.0

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 Reply: dev@nifi.apache.org Date: November 26, 2020 at 04:55:56 To: dev@nifi.apache.org Subject: [DISCUSS] Release

Re: request to review NIFI-7738, Provenance Search Events - add reverse query capability

t is important in how we think about this. Thanks On Thu, Oct 8, 2020 at 11:13 AM Otto Fowler wrote: > Anyone can review, but you need at least one committer approval / review > to get a pr landed. > > > On October 8, 2020 at 12:17:17, Joe Witt (joe.w...@gmail.com) wrote: > > Hel

Re: request to review NIFI-7738, Provenance Search Events - add reverse query capability

Anyone can review, but you need at least one committer approval / review to get a pr landed. On October 8, 2020 at 12:17:17, Joe Witt (joe.w...@gmail.com) wrote: Hello Anyone can do a review of the code and build and feasibility of a change. It only requires commit privileges to actually

Re: Teradata and Nifi

I believe this still applies: https://community.cloudera.com/t5/Support-Questions/Teradata-and-NIFI/td-p/211964 On August 28, 2020 at 10:54:34, Urooj, Harisa (harisa.ur...@teradata.com) wrote: We’re trying to do bulk loading of data in Teradata using NIFI. Is that possible in NIFI? Currently

Re: From one flowfile to two...

Thanks for writing that up! On August 27, 2020 at 17:49:07, Russell Bateman (r...@windofkeltia.com) wrote: In case anyone cares, https://www.javahotchocolate.com/notes/nifi-custom.html#two-split-from-one On 8/27/20 11:15 AM, Andy LoPresto wrote: > Russell, > > Glad you found a working

Re: [VOTE] Release Apache NiFi 1.12.0

+1 - release helper - ran built instance - imported template - ran external python program ( dotifi ) which uses nipyapi + rest api On August 14, 2020 at 14:02:00, Bryan Bende (bbe...@gmail.com) wrote: +1 (binding) Verified everything in the release helper and ran a secure instance with a

Re: [ANNOUNCE] New Apache NiFi Committer Marton Szasz

Belated congratulations! On August 3, 2020 at 04:02:17, Arpad Boda (ab...@apache.org) wrote: Apache NiFi community, On behalf of the Apache NiFI PMC, I am very pleased to announce that Marton has accepted the PMC's invitation to become a committer on the Apache NiFi project. We greatly

Re: [nifi] branch main created (now 239a2e8)

kers? :) I just rebased it against the laster master branch, should >>>> I be using main as of this point, or is there more work to be done >>>> before we switch over? >>>> br/>>>>> Thanks, < >>>> Matt >>>> br/>>>&g

Re: [nifi] branch main created (now 239a2e8)

t; > > > > Might also be a good time to think about closing out old PRs (like age > > > > 1.5 years). > > > > > > On Mon, Jul 6, 2020 at 10:49 PM Otto Fowler > > wrote: > > > > > > > So, should we rebase our outstanding PR’s? Should all outs

Re: [nifi] branch main created (now 239a2e8)

So, should we rebase our outstanding PR’s? Should all outstanding PR’s get a note? On July 6, 2020 at 17:57:25, Andy LoPresto (alopre...@apache.org) wrote: Apache Infra completed the change. Everything looks ok from my end but as I made the initial change, can someone else verify that their

Re: Informing users fields are deprecated

There are jira issues out there like : https://issues.apache.org/jira/browse/NIFI-6043 On July 6, 2020 at 09:28:35, Bryan Bende (bbe...@gmail.com) wrote: Do you mean a property on a processor/controller service? If so, there is no visual indicator that I'm aware of, it would require adding

Re: [DISCUSS] rename master branch, look through code for other related issues

As long as it isn’t renamed to zeek or something, I think we should change it and not look back. On June 18, 2020 at 19:05:38, Mike Thomsen (mikerthom...@gmail.com) wrote: > As teammates and friends, it was an easy change, even if code was involved. And I assume much easier than having the

Re: [ANNOUNCE] New NiFi PMC member Drew Lim

Congratulations! On May 29, 2020 at 15:55:19, Tony Kurc (tk...@apache.org) wrote: 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. Drew has been doing an amazing job for several years making

Re: [ANNOUNCE] New NiFi PMC member Arpad Boda

Congratulations On May 29, 2020 at 15:48:10, Tony Kurc (tk...@apache.org) wrote: 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 contributor and

Re: Nifi tutorials

When you post them, you should tweet them and reference @apachenifi ! On May 26, 2020 at 15:48:53, Jeremy Dyer (jdy...@gmail.com) wrote: Of course! I think that would be very much appreciated by everyone. Get Outlook for iOS From: Russell

Re: Camel & Nifi

Great! Thanks for the blog! On May 26, 2020 at 02:15:24, ski n (raymondmees...@gmail.com) wrote: Wrote a tech blog on using Camel with Apache NiFi: https://medium.com/@raymondmeester/using-camel-and-nifi-in-one-solution-c7668fafe451 I thought I share it here, Raymond

Re: Persisting/loading NIFI flows for Docker deployment

r have I misunderstood your "silly question"? Cheers, Chris Sampson On Wed, 8 Apr 2020, 18:17 Otto Fowler, wrote: > Can I ask a silly question? Would the ability for nodes to load flows > from the registry make this easier? Would that even make sense? > > On April 8, 2

Re: ConsumeEWS

The ConsumeEWS processor has no special handling for multipart mime messages. It would need to be extended to have more control over the output. It looks like all you can do is specify headers to include or ignore. On April 8, 2020 at 13:02:21, Jisson Dennis (jissonden...@gmail.com) wrote: Hi

Re: Persisting/loading NIFI flows for Docker deployment

Can I ask a silly question? Would the ability for nodes to load flows from the registry make this easier? Would that even make sense? On April 8, 2020 at 12:52:19, Chris Sampson ( chris.samp...@naimuri.com.invalid) wrote: When first starting with NiFi (I've always used it in container form),

Re: Reading the incoming flowfile "twice"

it the flowfile where I left off from copying up to . On 3/30/20 8:25 PM, Otto Fowler wrote: > Can I ask why you would consume the whole stream when doing the non-sax > part? If you consume the stream right up to the sax part ( the stream POS > is at the start of the xml ) then you can

Re: Reading the incoming flowfile "twice"

Can I ask why you would consume the whole stream when doing the non-sax part? If you consume the stream right up to the sax part ( the stream POS is at the start of the xml ) then you can just pass the stream to sax as is can’t you? On March 30, 2020 at 16:23:27, Russell Bateman

Re: Make invokehttp to process faster to process more than 20k records

Do you have some other client calling that proves your API endpoint isn’t the bottleneck? Sorry if I missed that part and you already provided that. On March 18, 2020 at 09:29:27, Midhun Mohan (midhun.mo...@esginc.us) wrote: Hey Mike , I meant like when I try posting that many records it is

Re: [DISCUSS] Advanced search capabilities

+1 for the “bring your own golden hammer” approach On February 24, 2020 at 11:46:14, Mike Thomsen (mikerthom...@gmail.com) wrote: Another thing I forgot to throw out there was that you have an issue of latency if you use Janus or Neo4j. Lucene will almost certainly have substantially lower

  1   2   3   >