Re: Jira contributor access

Hi Jonathan, I've added you as a contributor to Jira. Looking forward to the contributions you have for NiFi! Regards, -- Mike On Mon, Mar 7, 2022 at 3:46 PM Jonathan Conti-Vock < jonathan.contiv...@gmail.com> wrote: > Hello, > > I'd like to request Jira contributor access. My Jira username i

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

+1 (binding) Verified checksums and signature of source release Built (with empty local repo) on CentOS Linux release 7.9.2009 Apache Maven 3.8.6 Java version: 1.8.0_362, vendor: Red Hat, Inc., runtime: /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.362.b08-1.el7_9.x86_64/jre Default locale: en_US, platfor

Re: [discuss] nifi 1.22 looking worthy at this point

Team, I observed something wonky with the UI in 1.22.0-SNAPSHOT (using the latest support/nifi-1.x branch) and I wrote NIFI-11560 [1] for it. I would be sad if we release 1.22.0 and then decide this is significant, so any extra eyes on it beforehand would be appreciated. [1] - https://issues.ap

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

+1 (binding) Ran through helper and verified checksums and signature of source release, verified git commit. Built on CentOS Linux release 7.9.2009, Apache Maven 3.8.6, Java version: 1.8.0_372, vendor: Red Hat, Inc., runtime: /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.372.b07-1.el7_9.x86_64/ Ran NiFi a

Re: Re: NiFi 1.19.1 TLS Cipher syntax

Martin, Java follows RFC naming conventions for cipher suites as mentioned in the Java Security standard names table [1]. It looks like the "TLS_AKE_WITH_"* cipher names you are trying to match are not used by Java. I found one site [2] that mentions them as cipher codes 0x1301-0x1305. >From RF

new PackageFlowFile processor

Devs, I can't find if this was suggested before, so here goes. With the demise of PostHTTP in NiFi 2.0, the recommended alternative is to MergeContent 1 file into FlowFile-v3 format then InvokeHTTP. What does the community think about supporting a new PackageFlowFile processor that is simple to

Re: new PackageFlowFile processor

in > implementation and config of merge content i think. What did you have in > mind for that? > > Thanks > > On Fri, Sep 8, 2023 at 6:53 AM Michael Moser wrote: > > > Devs, > > > > I can't find if this was suggested before, so here goes. With the d

Re: Custom-processor configuration suggestions

Unfortunately, Otto's ASCII art doesn't render nicely for me, but I agree with what I think he's saying. And it aligns nicely with what Joe said too. Create a custom controller service that has the job of loading your configuration data set. This service can provide methods in its API to do look

Re: Nifi in Kubernetes environment

There are many ways to run Apache NiFi in containers and Kubernetes. Have a look at NiFiKop, a kubernetes operator for Apache NiFi [1]. Note that it is a separate open-source project from Apache NiFi itself. [1] - https://github.com/konpyutaika/nifikop Regards, -- Mike On Mon, Nov 6, 2023 at

Re: [VOTE] Release Apache NiFi 1.24.0 (RC4)

+1 (binding) Built using maven wrapper on CentOS 7.9 with: Apache Maven 3.9.5 (57804ffe001d7215b5e7bcb531cf83df38f93546) Maven home: /home/mosermw/.m2/wrapper/dists/apache-maven-3.9.5/2021cb71 Java version: 1.8.0_382, vendor: Red Hat, Inc., runtime: /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.382.b05-1.

Re: Apache Nifi Installation Issues

Alex, The error occurs when NiFi tries to move the self-signed certificate it generated from /tmp/test-keystore-4089669996254362100.p12 to ./conf/keystore.p12. This is a very basic file operation, so something is up with your environment. I have not used WSL, so I suggest Googling "windows subsy

Re: UpdateAttribute Failure Relationship

Hi Dan, This has been discussed in the past, as you found with those two Jira tickets. Personally, I'm still not sure whether a new failure relationship on UpdateAttribute in 2.0 is a good approach. I have heard from some dataflow managers that would not want to go through their entire graph whe

Re: UpdateAttribute Failure Relationship

tions. > >>> Obviously > >>>> the processor would need an update to catch Expression Language > >>> exceptions > >>>> and then route conditionally to failure. > >>>> > >>>> Just thinking out loud. > >>>>

Re: Jira contributor access

Hello, The bbobcik user in Apache Jira has contributor access to the NiFi project. Is it not working for you? What action in Jira are you trying to do? -- Mike On Fri, Mar 1, 2024 at 9:48 AM Boleslav Bobcik wrote: > Hello, I just wanted to check whether my request for contributor access is

Re: How to unset a sensitive property

Hi Dan, You edit the property as usual, and when the text box appears showing the greyed-out "Sensitive value set" in the box, simply click anywhere in the text box and "Sensitive value set" will disappear. Then click the "OK" button and the value should be back to "No value set". -- Mike On Mo

Re: Build of 2.x failing on Centos 7

Perhaps this was an unintentional change to the nifi-web-ui from the NIFI-13035 PR that was merged recently? -- Mike On Fri, Apr 19, 2024 at 12:06 PM Dan S wrote: > Thanks David! > I did not have this problem the other day when I submitted a PR for > NIFI-12960. > > On Fri, Apr 19, 2024 at 12

Re: Build of 2.x failing on Centos 7

Thanks for explaining the intent, David, and it makes perfect sense. -- Mike On Fri, Apr 19, 2024 at 12:26 PM David Handermann < exceptionfact...@apache.org> wrote: > Mike, > > The change was intentional from my understanding as Node.js 16 reached > end of life last year [1]. Registry should al

Re: Desire to view more than 100 items within a queue

This issue was discussed in the past but never reached a consensus for an implementation that managed the concerns. My email is only to provide a link to that pull request and discussion, for those who are curious. https://github.com/apache/nifi/pull/4641 -- Mike On Tue, Apr 23, 2024 at 5:47 

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

+1 (binding) verified signature, hashes, commit ID had a glance at the README, LICENSE, NOTICE files built on: Apache Maven 3.9.6 Maven home: /home/mwmoser/.m2/wrapper/dists/apache-maven-3.9.6/a53741d1 Java version: 1.8.0_412, vendor: Red Hat, Inc., runtime: /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.

Re: ...not the most recent version of this FlowFile within this session...

Wow, thanks for this information! Just last week I saw code that modified attributes in a stream: flowFile.getAttributes().entrySet().stream().filter(e -> e.getKey().startsWith("foo")) .forEach(e -> session.putAttribute(flowFile, "original-" + e.getKey, e.getValue())); and I wondered how tha

Re: ...not the most recent version of this FlowFile within this session...

; > ``` > final Map attributes = new HashMap<>(); > flowFile.getAttributes().forEach( (key, value) -> { > if (key.startsWith(“foo”)) { > attributes.put(“original-“ + key, value); > } > } > > flowFIle = session.putAllAttributes(flowFile, attributes); >

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

+1 (binding) Stepped through the release helper to verify the things. Apache Maven 3.9.6 Java version: 21.0.3 Red Hat Enterprise Linux 8.9 Upgraded NiFi from 2.0.0-M2 to 2.0.0-M3. Upgraded NiFi Registry from 2.0.0-M2 to 2.0.0-M3 Tested a few flows with no problems. -- Mike On Thu, May 16, 202

Re: [DISCUSS] Progress Update on new UI

Would we prefer Jira tickets or dev emails to discuss design of the new UI? For example: On the Summary page the old UI could show 25 rows in the table before scrolling but the new UI shows 14 rows. Is there any way we can make the height of each row a bit smaller to fit more on the screen? I do

Re: [DISCUSS] 1.x Maintenance

My opinion is that the NiFi 1.x line is already in maintenance and doesn't need new features or APIs, but bug fixes are still important to get in, and security fixes are still critical. That said, this is an open source community-driven project, so if you can find contributors and committers that

Re: [VOTE] Release Apache NiFi 1.6.0

+1 (binding) Ran through release helper to verify the release and run NiFi on Ubuntu 16.04. It worked as expected with no new comments to add. -- Mike On Fri, Mar 23, 2018 at 4:02 PM, Scott Aslan wrote: > +1 (binding) > > - Ran through release helper > - Setup secure NiFi and verified a test

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

+1 (binding) Followed helper to verify release, built on Ubuntu 16.04 LTS, ran the application successfully. -- Mike On Wed, Mar 28, 2018 at 2:01 PM, Mark Payne wrote: > +1 (binding) > > Was able to build successfully and start application. Created some simple > flows to verify expected behav

Re: Firefox - Slower movements when moving around the canvas

Adding a data point: using Firefox for Linux 64-bit, I see no difference between Firefox 58.0.2 and 59.0.2. Neither exhibit a slow canvas with the NiFi UI. -- Mike On Tue, Apr 3, 2018 at 3:24 PM, Pierre Villard wrote: > Yep, same here Mike, back to square one I guess... > One additional remar

Re: [EXT] Suggestion: Apache NiFi component enhancement

Hi Sivaprasanna, After reading your first email, I thought it would be a lot of work for little benefit, because I think you would have needed to touch many parts of the framework. After reading your clarification, the scope seems more limited. It's definitely an interesting idea, and here are m

Re: [ANNOUNCE] New NiFi PMC member Mike Thomsen

Congrats and a big thank you for your work! On Wed, Jun 6, 2018 at 10:10 PM, Scott Aslan wrote: > Congrats > > On Wed, Jun 6, 2018, 9:03 PM Matt Burgess wrote: > > > Congratulations Mike! Great to have you aboard, I appreciate your > > commitment and work ethic and looking forward to continued

unit test failures on master

Greetings NiFi dev: I'm getting unit test failures trying to build the master branch. [INFO] [INFO] Building nifi-runtime 1.8.0-SNAPSHOT [INFO] [INFO]

Re: unit test failures on master

erprint: 70EC B3E5 98A6 5A3F D3C4 BACE 3C6E F65B 2F7D EF69 > > On Jul 24, 2018, at 2:13 PM, Michael Moser wrote: > > Greetings NiFi dev: > > I'm getting unit test failures trying to build the master branch. > > [INFO] > ---

Re: [ANNOUNCE] New NiFi PMC member Kevin Doran

Congrats, welcome, and thank you for your work. On Tue, Jul 31, 2018 at 9:21 AM Otto Fowler wrote: > Congratulations! > > > On July 31, 2018 at 08:26:34, Tony Kurc (tk...@apache.org) wrote: > > NiFi Community, > > On behalf of the Apache NiFi PMC, I am pleased to announce that Kevin Doran > has

Re: [ANNOUNCE] New NiFi PMC member Jeremy Dyer

Congrats, welcome, and thank you for your work. On Tue, Jul 31, 2018 at 9:21 AM Otto Fowler wrote: > Congratulations! > > > On July 31, 2018 at 08:36:48, Tony Kurc (tk...@apache.org) wrote: > > All, > > On behalf of the Apache NiFi PMC, I am pleased to announce that Jeremy Dyer > has accepted

Re: Status of "event-driven" scheduling

Hi Joe, I'm guessing here, but I think the Event Driven scheduling was intended to be more efficient than Timer Driven scheduling, in the way that push notifications should be more efficient than polling. In practice, I'm not sure anyone has measured the difference. I have seen folks use Event D

Re: [External] Re: Expression language and NiFi registry

For the specific case of "host name of the AMQP processors", EL support for that property was added to NiFi in NIFI-5489 [1] which will be released with NiFi 1.8.0 (available real soon!) [1] - https://issues.apache.org/jira/browse/NIFI-5489 -- Mike On Wed, Oct 24, 2018 at 3:06 PM Pierre Villard

Re: [DISCUSS] Extension Registry

I have thought about this in the past, too. Here's a scenario where I could never really lay down an approach I was happy with. Consider that a NiFi user searches the NiFi registry and finds the PutMongo processor. Registry knows the PutMongo processor is in the nifi-mongodb-nar, and through its

Re: [DISCUSS] Early, voluntary relocation to GitBox

+1 from me, sounds great. On Mon, Dec 10, 2018 at 4:07 AM Arpad Boda wrote: > +1 (for being the guinea pig __ ) > > On 09/12/2018, 04:01, "Aldrin Piri" wrote: > > Thanks to those of you that responded. > > I think my tentative plan is to give this a few more days to see if > there >

Re: SSD fatigue

Hello Phil, When supporting an I/O intensive application such as NiFi at the enterprise level, you have to plan for failures in your storage layer. Disks are going to fail and you only get to choose how that failure will affect your system. Here are some things to think about. + Use RAID for da

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

+1 (binding) verified the release using the helper, ran some flows, and ran in a Docker container. -- Mike On Tue, Feb 19, 2019 at 5:10 PM Tony Kurc wrote: > +1 (binding) > > - Went through helper on ubuntu 16.04 (x86) without issue > - ran through some very simple flows > > > On Tue, Feb 19,

Re: GetHttp always givues error "SocketTimeotException,Read timedOut"

Hello, I noticed from your screenshot that your GetHTTP is using a URL with "http://"; but you also have an SSL Context Service defined. If your endpoint is using SSL/TLS then your URL should begin with https://. However, if your endpoint uses plaintext HTTP, then I suggest trying to configure Ge

Re: [ANNOUNCE] New Apache NiFi PMC member Peter Wicks

Great work, Peter. Congrats! On Thu, May 30, 2019 at 8:05 PM Marc Parisi wrote: > Congrats! > > On Thu, May 30, 2019, 2:58 PM Jeff wrote: > > > Welcome to the PMC, Peter! Congrats! > > > > On Thu, May 30, 2019 at 2:45 PM Tony Kurc wrote: > > > > > Congratulations Peter!! > > > > > > On Thu,

Re: [ANNOUNCE] New Apache NiFi Committer Kotaro Terada

Congrats on becoming a NiFi committer, Kotaro! On Thu, Oct 24, 2019 at 1:06 PM Otto Fowler wrote: > Congratulations! > > > > > On October 24, 2019 at 09:50:17, Aldrin Piri (ald...@apache.org) wrote: > > Apache NiFi community, > > On behalf of the Apache NiFI PMC, I am very pleased to announce

Re: [DISCUSS] Closing in on a 0.x release

;> personally would rather see a release with some fixes and a couple > known > > >> issues than holding off for "perfection", especially as a lot of our > > effort > > >> is on 1.x. Are you asking if effort would be wasted if patches were > > >

Re: [DISCUSS] Closing in on a 0.x release

9:56 AM, Joe Witt wrote: > Team, > > Mark Payne just opened this one: https://issues.apache.org/ > jira/browse/NIFI-2874 > > It should probably be in this release if able. > > Thanks > Joe > > On Mon, Oct 3, 2016 at 10:48 AM, Michael Moser wrote: > &

Re: [DISCUSS] Closing in on a 0.x release

looks like the two tickets NIFI-2429, > NIFI-2874 were merged in and NIFI-2774 is still under discussion. Oleg, > Mike, are we feeling like we're close, or would this best fit in the next > 0.x release? > > Tony > > > > On Fri, Oct 7, 2016 at 3:21 PM, Michael Moser wr

Re: [DISCUSS] Closing in on a 0.x release

NIFI-2774 is now complete and merged to both master and 0.x branches. +1 on a release from the 0.x branch now. -- Mike On Mon, Oct 10, 2016 at 10:24 AM, Michael Moser wrote: > I feel that Oleg was really close, and it would be nice for this to be in > 0.7.1 but it isn't neces

Re: Error: Self-suppression not permitted

Devin, This sounds a lot like the issue documented in NIFI-2551 [1]. Since you are using NiFi 0.7.0, you might try to build the latest code in the 0.x branch and see if this version resolves your problem. -- Mike [1] - https://issues.apache.org/jira/browse/NIFI-2551 On Wed, Oct 12, 2016 at 6:

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

+1 (non-binding) git tag and commit ID verified Downloaded nifi-0.7.1-source-release.zip and verified hashes Source builds with RAT checks using Java 1.7.0_79 Application runs and a few templates work as expected on CentOS 6 On Tue, Oct 18, 2016 at 1:38 PM, Joe Skora wrote: > Yeah, I'll get m

Re: [DISCUSS] Provided dependency on bcprov-jdk15on

I would like to point out that some very common dependencies have been placed into the nifi-standard-services-api-nar. This nar is a Nar-Dependency-Id of several other nars. Many of these other nars also include the same dependencies, which would not be used by the nar class loader. In particula

NiFi processor validation

All, I would like to propose a fundamental change to processor validation based on observations in https://issues.apache.org/jira/browse/NIFI-2996. I would like to validate processors only when they are in the STOPPED state. The properties on a processor in the RUNNING state should always be vali

Re: NiFi processor validation

ly. This presents its own challenges > but > >>> would also be helpful. We should try to avoid calling into user code > in any > >>> web thread. > >>> > >>> Matt > >>> > >>> [1] https://issues.apache.org/jira/browse/NIFI-950 >

Re: [DISCUSS] NiFi 1.1.0 release

After seeing "Repositories now support rollback" in the release notes and reading NIFI-2854 [1], I have a question. Are repositories created using NiFi 1.0.0 compatible with NiFi 1.1.0 software? This is the goal that the ticket seems to indicate with 1.1.0 onward, but it's not clear whether 1.0.0

Re: [DISCUSS] NiFi 1.1.0 release

t; latest NiFi 1.1.0-SNAPSHOT. Moved the repos over. And it came up > > perfectly with all the queue data ready to roll. > > > > Thanks > > Joe > > > > On Tue, Nov 22, 2016 at 12:16 PM, Michael Moser > wrote: > >> After seeing "Repositories now supp

Re: ActiveMQ trust store issues

Joe, Have you seen https://issues.apache.org/jira/browse/NIFI-3230? You might try the latest code on the master branch to see if it fixes your problem. The JIRA ticket also offers a workaround by using a failover URI. -- Mike On Wed, Jan 11, 2017 at 8:20 PM, Joe Gresock wrote: > Hi folks, >

Re: PutFile,PutHDFS handle similar properties differently

It appears that PutFile "Permissions" supports expression language which makes static validation harder, whereas PutHDFS "Permissions umask" does not support expression language. I would prefer the PutFile approach. Making more properties support expression language seems reasonable. I think this

Re: [VOTE] Establish Registry, a sub-project of Apache NiFi

I am in favor of the concept but the name made me pause. I did a Google search of "apache registry" and found an existing Perl module called Apache::Registry. Should I be worried about potential naming confusion? -- Mike On Fri, Feb 10, 2017 at 12:16 PM, Oleg Zhurakousky < ozhurakou...@hortonw

Re: [VOTE] Establish Registry, a sub-project of Apache NiFi

then I do agree we would likely have to call it "NiFi > > > > Registry". > > > > > > > > > > > > On Fri, Feb 10, 2017 at 12:21 PM, Joe Percivall < > jperciv...@apache.org > > > > > > wrote: > > > >> I 100% agree with M

Re: [VOTE] Release Apache NiFi 0.7.2

I'm sad that 0.7.2 does not contain some of the other bug fixes currently on the 0.x branch. It doesn't seem like it would have cost very much to just include them. +0 (non binding) -- Mike On Thu, Feb 16, 2017 at 11:42 PM, Andy LoPresto wrote: > Hello, > > I am pleased to be calling this vo

Re: [ANNOUNCE] New Apache NiFi Committer Jeff Storck

Congrats Jeff! On Tue, Feb 21, 2017 at 4:25 PM, Joe Skora wrote: > Congrats and welcome aboard Jeff! > > On Tue, Feb 21, 2017 at 4:01 PM, Tony Kurc wrote: > > > Nice work Jeff! > > > > On Tue, Feb 21, 2017 at 2:41 PM, Aldrin Piri wrote: > > > > > On behalf of the Apache NiFI PMC, I am very pl

Re: [ANNOUNCE] New Apache NiFi PMC Member - James Wing

Congratulations James, and thanks for your dedication to NiFi. On Wed, Feb 22, 2017 at 9:58 AM, Aldrin Piri wrote: > Team, > > On behalf of the Apache NiFi PMC, I am pleased to announce that James Wing > has accepted the PMC's invitation to join the Apache NiFi PMC. We > greatly appreciate all

Re: [ANNOUNCE] New Apache NiFi PMC Member - Oleg Zhurakousky

This is great news, congrats Oleg! On Wed, Apr 5, 2017 at 11:41 AM, Bryan Rosander wrote: > Congrats Oleg! > > On Wed, Apr 5, 2017 at 9:53 AM, Oleg Zhurakousky > wrote: > > > Thank you all! > > > > > > *Joe Percivall* > > > e: joeperciv...@gmail.com > > > > >

Re: [ANNOUNCE] New Apache NiFi Committer Bin Qiu

Welcome aboard, Bin, and congratulations. On Wed, Apr 5, 2017 at 11:44 AM, Marc wrote: > Congrats and well deserved for everything you've done! > > On Wed, Apr 5, 2017 at 11:42 AM, Bryan Rosander > wrote: > > > Congrats Bin! > > > > On Wed, Apr 5, 2017 at 9:52 AM, Oleg Zhurakousky > wrote: >

Re: Closing in on a NiFi 0.8.0 release?

All, I have started going through JIRA and identifying remaining issues against the 0.x branch to prepare for a release, and I've worked a couple of the JSON.org Cat-x license issues on that branch. I would like to volunteer to be release manager for a 0.7.3 release, if you will let me try. ;-)

Re: EncryptContent issues after NIFI-1257 and NIFI-1259

Hello, I believe the EncryptContent "Public Keyring File" property is expecting the binary key that you generated in step 1. You do not need to export the public key into ASCII format. Kind Regards, -- Mike On Wed, May 3, 2017 at 6:40 AM, Athar wrote: > I am getting this issue in even nifi 1

Re: [VOTE] Release Apache NiFi 1.2.0

+0 (non-binding) In 1.2.0, the nifi-standard-bundle now includes calcite-core-1.12.0.jar, and the nifi-standard-nar has Apache Calcite mentioned in its NOTICE. However we don't seem to have Apache Calcite in the assembly NOTICE. Does this qualify for a -1 vote? We have also upgraded the version

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

+1 (non-binding) Release this package as nifi-1.2.0 There was definitely a lot of work that went into this release, many thanks to all. On Mon, May 8, 2017 at 2:23 PM, Mark Payne wrote: > +1 (binding). > > Was able to complete full build w/ contrib check on OSX. Verified > checksums and that a

Re: Closing in on a NiFi 0.8.0 release?

the RM role a go and it is > very appreciated particularly on 0.x where it isn't as easy to put > attention/cycles. > > Thanks > Joe > > On Wed, Apr 12, 2017 at 6:17 PM, Michael Moser wrote: > > All, > > > > I have started going through JIRA and id

Re: Closing in on a NiFi 0.8.0 release?

Witt wrote: > Mike > > it looks like there is only a single 0.7.3 ticket but there are a lot > of 0.8.0 tickets. Are you planning to cherry-pick the needed commits > into the support/0.7.x branch? > > Thanks > Joe > > On Thu, May 11, 2017 at 1:55 PM, Michael Moser

[VOTE] Release Apache NiFi 0.7.3

Hello Apache NiFi community, I am pleased to be calling this vote for the source release of Apache NiFi nifi-0.7.3. The source zip, including signatures, digests, etc. can be found at: https://repository.apache.org/content/repositories/orgapachenifi-1105 The Git tag is nifi-0.7.3-RC1 The Git com

Apache NiFi 0.7.3 RC1 Release Helper Guide

Hello Apache NiFi community, Please find the associated guidance to help those interested in validating/verifying the 0.7.3 release so they can vote. # Download latest KEYS file: https://dist.apache.org/repos/dist/dev/nifi/KEYS # Download the key used to sign this release: https://people.apache.

Re: Apache NiFi 0.7.3 RC1 Release Helper Guide

le? >> >> Thanks, >> >> James >> >> On Sun, May 14, 2017 at 5:36 PM, Michael Moser wrote: >> >>> Hello Apache NiFi community, >>> >>> Please find the associated guidance to help those interested in >>> validat

Re: adding additionals content viewers

I was going to add a JIRA to add this to the Developer's Guide, but I see [1] one already exists. -- Mike [1] - https://issues.apache.org/jira/browse/NIFI-479 On Wed, May 17, 2017 at 1:18 PM, Joe Witt wrote: > wow - i think i need to learn more about this NiFi thing. That is awesome! > > On W

[RESULT][VOTE] Release Apache NiFi 0.7.3

Apache NiFi Community, I am pleased to announce that the 0.7.3 release of Apache NiFi passes with 5 +1 (binding) votes 0 -1 (binding) votes 0 0 votes 0 -1 votes Thanks to all who helped make this release possible! Here is the PMC vote thread: https://mail-archives.apache.org/mod_mbox/nif

[ANNOUNCE] Apache NiFi 0.7.3 release

Hello The Apache NiFi team would like to announce the release of Apache NiFi 0.7.3. 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, transformation, an

Re: Binaries in embedded redis jar files

Whoa, this causes serious concerns for me. While I can understand that the source code is the official ASF artifact, the nifi.apache.org site provides convenience binaries which I'm sure many people use. When NiFi 1.4.0 releases, we should write very conspicuous warnings on the Downloads page to a

Re: Binaries in embedded redis jar files

19 PM, Michael Moser wrote: > Whoa, this causes serious concerns for me. While I can understand > that the source code is the official ASF artifact, the nifi.apache.org > site provides convenience binaries which I'm sure many people use. > When NiFi 1.4.0 releases, we should write ver

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

+1 (non-binding) Verified source package per release helper. Built on Ubuntu 14.04, all unit tests and contrib-check pass. Built on Windows 10, some unit tests fail and contrib-check fails on "nifi-poi-processors: Too many files with unapproved license" but I think this was expected. The build wi

Re: [ANNOUNCE] New NiFi PMC member Scott Aslan

Thank you for your work, Scott, and congrats on joining the PMC! -- Mike On Mon, Dec 4, 2017 at 7:02 AM, Rob Moran wrote: > Awesome – congrats Scott!! > > On Mon, Dec 4, 2017 at 4:28 AM Pierre Villard > > wrote: > > > Congrats Scott, well deserved! > > > > 2017-12-03 13:58 GMT+01:00 Scott Asl

Re: Unable to checkpoint FlowFile Repository (No space left on device)

Greetings Ben, The "No space left on device" error can also be caused by running out of inodes on your device. You can check this with "df -i". -- Mike On Tue, Dec 12, 2017 at 1:36 AM, 尹文才 wrote: > sorry that I forgot to mention the environment that caused this problem, > I'm using the lates

Re: Unable to checkpoint FlowFile Repository (No space left on device)

les in all repository folders and restarted > >> the system, I couldn't see the error again. I will continue to track the > >> problem to see what's causing it, but it seems not relevant to the inode > >> use-up reason you mentioned. Thanks. > >> > >

Re: [ANNOUNCE] New NiFi PMC member Marc Parisi

Congrats Marc, and thanks for your work on the project. On Fri, Dec 15, 2017 at 6:52 AM, Rob Moran wrote: > Congratulations, Marc! > > On Fri, Dec 15, 2017 at 4:31 AM Pierre Villard < > pierre.villard...@gmail.com> > wrote: > > > Congrats Marc!! > > > > 2017-12-15 6:38 GMT+01:00 Jeff : > > > >

Re: Penalized FlowFiles still cause Processor Invocations

This behavior is known and there is an open JIRA ticket [1] for it. It's not great for the processor's onTrigger() to be continually called without a flowfile, but it's also not a great user experience to do nothing and show 0 tasks executed, which leaves the end user with no idea why the processo

Re: Nifi "event driven" scheduling strategy Custom Processor

Hello! An "event" in the context of the NiFi @EventDriven annotation is the arrival of a flow file in the queue that is an input to a processor. The only purpose of @EventDriven is to save system resources when compared to the default Timer Driven strategy, in which a processor polls its input qu

Re: [Non-DoD Source] Re: Moving from version 1.1.2 to 1.4.0

Steven, Joe and Bryan's suggestions are best, but there is another way to try to resolve your issue, It comes with a large "Beware of class loaders" sign, but it can work. Your custom nar can be built so that it depends on the classes found in nifi-standard-nar, by using a nar dependency. A nar

Re: 答复: Re: 答复: Re: NiFi starts very slowly

I was thinking that with 16000 processors, you would need a large amount of heap space allocated to the JVM. A small heap would slow NiFi's ability to do its work, because the JVM garbage collector would be consuming more CPU time than what is healthy. A 64 GB heap size, allocated in the NiFi boo

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

+1 (binding) release this package as nifi-1.5.0 Verified release package, built and executed cleanly and passed some regression testing. Thanks to everyone for continued efforts to improve and expand NiFi's capabilities! -- Mike On Thu, Jan 11, 2018 at 1:01 PM, Aldrin Piri wrote: > +1, bind

Re: [DISCUSS] Apache NiFi distribution has grown too large

Long term I would also like to see #3 be the solution. I think what Joseph N described could be part of the capabilities of #3. I would like to add a note of caution with respect to reorganizing and releasing extension bundles separately: - the burden on release manager expands because many m

Re: [DISCUSS] Apache NiFi distribution has grown too large

And of course, as I hit I thought of one more thing. We could keep all of the code in 1 git repo (1 project) but the nifi-assembly part of the build could be broken up to build core NiFi separately from the tar/zip functional grouping of other NARs. On Fri, Jan 12, 2018 at 5:01 PM, Michael

Re: Empty String in UpdateAttribute

Hi Mark, After reading the JIRA [1] and the PR for the UpdateAttribute modifications, I believe this was simply an unintended consequence of the code changes. If you would like to write a new JIRA, then I'm sure we can restore the "Set Empty String" functionality when not storing attributes in lo

Re: Unable to start NiFi

Hello, I see your VM arguments contain 2 "-Xms" and 0 "-Xmx" arguments: -Xms2048m -Xms2048m Please check your nifi/conf/bootstrap.conf file to make sure the JVM memory settings show -Xms2048m -Xmx2048m Regards, -- Mike On Fri, Jan 19, 2018 at 6:25 AM, 尹文才 wrote: > Hi guys, one of my

Re: [DISCUSS] Proposal for an Apache NiFi sub-project - NiFi Fluid Design System

There are compelling pros and easily identifiable cons to placing UI components into their own project. I don't have anything to add there. Please, however, consider a different name. "Fluid Design System" is generic to the point of giving no cognitive clue about what it actually is. And witho

Re: RAT check failure

Hi Mark, Try to do a "mvn clean -Pinclude-grpc" first, then do your "mvn -Pcontrib-check install". By default the nifi-grpc-bundle is not included in any phase of the maven build. You have probably built nifi-grpc-bundle in the past in your workspace. -- Mike On Sat, Mar 10, 2018 at 12:13 PM,

Re: [discuss] nifi 1.6.0 release

I would like to finish up NIFI-3599 , which just needs some contributer / review agreement. -- Another Mike On Mon, Mar 12, 2018 at 1:28 PM, Mike Thomsen wrote: > If we could get this patch for HBase visibility labels merged before, I'd > appreci

Re: [discuss] nifi 1.6.0 release

: > > > > Mike, Michael, > > > > Both items noted seem fair for inclusion in whatever release vehicle > > follows them being merged but neither look like they'd impact release > > timing. Please advise if I'm misreading either of those. > > >

Re: nifi-0.3.0 release

All, As a suggestion for the future, at least after NiFi reaches 1.0, I think a bug fix release such as a 0.2.1 would definitely happen in a scenario like this. Even after 0.3.0 is available for download, if you don't recommend that people use 0.2.0 due to major bugs, then you should replace it w

Re: nifi-0.3.0 release

tate as per our version scheme. > > I do agree for major releases like 1.0.0 we have a need to discuss as a > community how long to support pre 1.0 as well as 1.x. This is based on our > published versioning model. > > Does this sound reasonable to you? > > Thanks > Joe > On

Re: [DISCUSS] Feature proposal: Read-only mode as default

"undo" seems to be the stretch goal that I think that would solve most concerns of unintended modifications to a graph. +1 Meanwhile, I'd like to caution against confirmation dialogs. Extra clicks quickly annoy users while they work. I suggest no dialog when deleting a single queue or processor

Re: Getting yesterday's date, or getting date offsets in general?

Russell, Try this expression in your Remote Path: /logs/${now():toNumber():minus(8640):format('-MM-dd')} -- Mike On Wed, Sep 9, 2015 at 4:53 PM, Russell Whitaker wrote: > I'm setting up a GetSFTP processor to run every morning to > download files expected in a regular location named b

Re: NiFi service fails to start after removing processor from NAR

Rick, If you had an instance of your GetFileAttributes processor on your graph then NiFi will fail to start if you remove the processor from your NAR. It still has the GetFileAttributes in your flow.xml.gz and NiFi is trying to instantiate it. If you can start NiFi with your old NAR, then remove

Re: [ANNOUNCE] New Apache NiFi Committer Michael Moser

gt; > On behalf of the Apache NiFI PMC, I am very pleased to announce that > > Michael Moser has accepted the PMC's invitation to become a committer > > on the Apache NiFi project. We greatly appreciate all of Michael's > > hard work and generous contributions to the

  1   2   >