Re: MINIFI-350 minifi-cpp end-to-end integration testing framework

Great idea, Andy! Additional types of automated tests would help the minifi-cpp project significantly, and I think your proposal is an appropriate way to add integration tests for the minifi agent. This sounds like a great way to verify expected behavior of processors and the system of

Re: minifi-cpp config.yml case-sensitivity

Good catch, Andy. I agree the preferable course of action here would be to make MiNiFi CPP's yaml config parser case-insensitive. Kevin On 7/13/17, 11:09, "Andy Christianson" wrote: All, It appears that the properties in the config.yml are

Re: RTC clarification

I am in favor of allowing Scenario A and leaving it up to the committer / submitter to determine if the review is sufficient to merge or if an additional review(s) should take place. I think for committers will know the difference between, say, a documentation update or minor enhancement / fix

Re: why cant nifi perform user authentication over http？

Hi, You are correct, NiFi requires an encrypted connection for user authentication. This is because client identity is established in one of two ways: - user name & password, which should not be sent over a non-encrypted connection - client certificate in a two-way TLS (HTTPS) connection I

Re: why cant nifi perform user authentication over http

nifi`s code more efficiently, or if there are some other way to get what i want. As you can see my English is poor, thanks for you patience. Thanks for your reply. Best Regards YuNing On 2017-07-21 19:07 (+0800), Kevin Doran <kdoran.apa...@gmail.co

Re: Separate MiNiFi projects in JIRA

s might be overlooked when a ticket is created. On Mon, Aug 21, 2017 at 11:37 AM, Andy Christianson < achristian...@hortonworks.com> wrote: > Making it required sounds like an improvement, at the very least. > > -Andy I.C. > ____

Re: Correlate Processor ID in Logs

Hi Karthik, A processor's metadata, including its name and parent processor group ID, are accessible via the NiFi REST API [1] via GET /processors/{id}, which returns: { ... "component": { "id": "value", "parentGroupId": "value", "name": "value",

Re: [DISCUSS] NiFi MiNiFi C++ 0.2.0 Release

Hi Aldrin, One other issue came up in testing, which is that using the config.yml in the README file throws the following error: HW13384:nifi-minifi-cpp-0.2.0 brosander$ bin/minifi.sh run libc++abi.dylib: terminating with uncaught exception of type

Re: [ANNOUNCE] New Apache NiFi PMC Member - Yolanda Davis

Congratulations, Yolanda! As everyone has said, very well deserved! Thanks for all you do for the NiFi project and community. Kevin On 5/17/17, 22:11, "Tony Kurc" wrote: On behalf of the Apache NiFi PMC, I am pleased to announce that Yolanda Davis has accepted the

Re: [VOTE] Release Apache NiFi MiNiFi 0.2.0

+1, non-binding verified: - sigs & hashes -- bonus points for the md5 hash end in "*face" - full build with contrib check - reviewed license, readme, notice - ran with a simple flow config and verified behavior potential improvements: - README mentions mailing list and IRC. We should add the new

Re: [ANNOUNCE] New Apache NiFi Committer Marc Parisi

Congratulations, Marc! Very well deserved. Thanks for your contributions and generosity with sharing your technical knowledge. _ From:

Re: [VOTE] Release Apache NiFi 1.3.0

+1 (non-binding), release this package as nifi-1.3.0 Verified hash, tag. Full contrib-check build. Ran a simple site-to-site test and was able to send flow files. On 6/5/17, 13:54, "Matt Gilman" wrote: Hello, I am pleased to be calling this vote for the

Re: MiNiFi CPP indentation confusion (Re: MINIFI-244)

Hi Andy, I’ll let a minify-cpp veteran jump in if I have this wrong, but I believe we are following the Google C++ Style Guide [1]. As it is my first time following this style, it caused me to do a double take as well :-) The Google C++ Style Guide does specify entries under public, protected,

Re: "Flatten" JSON

+1 for adding a FlattenRecord processor. I can think of a few scenarios in which it would be quite useful, and it would be convenient if it could be accomplished without JOLT. Thanks, Kevin On 9/15/17, 09:16, "Nicholas Hughes"

Re: Dockerfile and Docker Hub Management

Thanks, Aldrin. I'm a +1 for a separate NiFi Docker project and release process, allowing improvements to the containerization of NiFi artifacts to be made independently from the artifacts (and their source files). I have observed many community members maintaining their own NiFi Dockerfiles

Re: Reg. Nifi Clustering Load Balancing

Hi Nishant, A HTTP load-balancer as Bryan suggests is a good option for server-side load balancing so that your client only needs to keep track of a single URL. In addition to the options Bryan mentioned, which are great, most cloud providers offer managed load balancing services, which many

Re: Having the ability to disable controlling mechanism for agents

Hey Marc, Thanks for kicking off this discussion. I think I would be in favor of allowing MiNiFi Agent users to disable C2 should they desire, without excluding it from the build. So long as we're supporting a build configuration that would remove C2, it seems to me it should be feasible to

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

+1, non-binding - Verified hashes - Full build with contrib-check passes - Was able to run nifi server and send flow files to remote input port over s2s protocol. Web UI and API working as expected. Platform: Apache Maven 3.5.0 (ff8f5e7444045639af65f6095c62210b5713f426;

Re: Separate MiNiFi projects in JIRA

Would it suffice to make the existing 'component' field _required_ at ticket creation time, and having components consist of 'C++', 'Java', & perhaps 'Both/All/*' as well? I imagine that is less effort than setting up and maintaining a separate project and solves the problem, unless there are

Re: [VOTE] Release Apache NiFi MiNiFI C++ 0.3.0 (RC1)

+1 (non-binding) Verified hashes, built and ran all tests, built docker and ran all integration tests. Ran a simple test flow. I did run into one minor issue, which is if virtualenv is configured with python3 by default then creating the virtual environment for the pytest integration tests

Re: [VOTE] Release Apache NiFi MiNiFI C++ 0.3.0 (RC2)

+1, non-binding. Verified hashes and signature; did full build with docker-verify and ran with a sample config flow. On 11/27/17, 11:59, "Marc" wrote: Hello Apache NiFi Community, I am pleased to call this vote for the source release of Apache NiFi MiNiFi

Re: [ANNOUNCE] New Apache NiFi Committer Andy Christianson

Congrats, Andy! Thanks for all the hard work on MiNiFi CPP! On 11/13/17, 19:39, "Tony Kurc" wrote: On behalf of the Apache NiFI PMC, I am very pleased to announce that Andy has accepted the PMC's invitation to become a committer on the Apache NiFi project. We

Re: [DISCUSS] Apache NiFi MiNiFi C++ 0.3.0

I agree. There's been a lot of great commits to master recently and it would be great to have them in a new release version. Thanks! Kevin On 11/1/17, 15:05, "Aldrin Piri" wrote: Hey folks, We've had a fair amount of work and enhancements to the framework

Re: [ANNOUNCE] New NiFi PMC member Jeff Storck

Congrats, Jeff! On 12/5/17, 11:49, "Tony Kurc" wrote: NiFi community, On behalf of the Apache NiFi PMC, I am pleased to announce that Jeff Storck has accepted the PMC's invitation to join the Apache NiFi PMC. We greatly appreciate all of Jeff's hard work and

Re: [DISCUSS] First Release of NiFi Registry

Thanks for kicking off this discussion thread, Bryan. I support prepping a release of NiFi Registry and making it version 0.1.0 as you propose. Thanks! Kevin On 12/7/17, 10:45, "Joe Witt" wrote: Bryan - very exciting and awesome. Having experimented with the

Re: [ANNOUNCE] New NiFi PMC member Scott Aslan

Congrats, Scott! Keep crushing it! Get Outlook for iOS From: Joe Witt Sent: Saturday, December 2, 2017 7:27:35 PM To: dev@nifi.apache.org Subject: Re: [ANNOUNCE] New NiFi PMC member Scott Aslan congrats scott and thanks

Re: ASF -> GitHub sync

Was it a large set of changes? I've seen this happen before where a large commit fails to sync to github. It's not a problem usually as the next commit usually triggers the mirror sync again and github "catches up". On 5/11/18, 08:50, "Mike Thomsen" wrote: I

[DISCUSS] Apache NiFi Registry 0.2.0

Hi everyone, There have been a lot of great improvements to Apache NiFi Registry since the initial release, and I'd like to start a discussion about releasing 0.2.0. There are only a few outstanding issues that have been marked for 0.2.0 in JIRA [1]: - NIFIREG-172 adds a self-hosted Swagger

Re: nifi not running (installation problem) - brew

The version of NiFi you are using (1.6.0) requires Java 8 (jre or jdk 1.8). Regards, Kevin On 6/7/18, 09:38, "kirilzilla" wrote: Hi, im writing my bachelor thesis and would like to use apache nifi. im using macOS 10.13.5 right now and installed nifi over brew packet manager "brew

Re: [DISCUSS] Change of Cluster Flow Inheritance

Hi Mark, Thanks for the great write-up! I support your proposal. It seems a logical improvement based on your description of how fingerprinting works today, the original problem it was trying to solve, and the proposed alternative. I am not an expert on how NiFi clustering is implemented, so

[VOTE] Release Apache NiFi Registry 0.2.0

Hello, I am pleased to call this vote for the source release of Apache NiFi Registry 0.2.0. The source zip, including signatures, digests, etc. can be found at: https://dist.apache.org/repos/dist/dev/nifi/nifi-registry/nifi-registry-0.2.0/ The Git tag is nifi-registry-0.2.0-RC1 The Git commit

Apache NiFi Registry 0.2.0 RC1 Release Helper Guide

Hello Apache NiFi community, Please find the associated guidance to help those interested in validating/verifying the Apache NiFi Registry release so they can vote. # Download latest KEYS file: https://dist.apache.org/repos/dist/dev/nifi/KEYS # Import keys file: gpg --import KEYS # [optional]

Re: Apache NiFi Registry 0.2.0 RC1 Release Helper Guide

ouble with running secure NiFi and > > the registry together (both secure). Can someone point me to build > > instructions for the Registry's docker image so I can try to replicate > > using 0.2 RC1? > > > > Thanks, > > > > Mike > >

Re: [VOTE] Release Apache NiFi Flow Design System 0.1.0 RC3

+1 (non-binding) Completed all the steps of the helper guide and played with the demo app. Verified the LN and Readme. Also verified version strings in the latest RC 3. Nice work on this everyone and thanks for RM'ing this initial release, Scott! Thanks, Kevin On 6/12/18, 10:12, "Matt

Re: [DISCUSS] Release candidate timeframe for Apache NiFi 1.7.0

This sounds like a good release plan / schedule for the upcoming versions of the sub projects. Thanks, Andy. Kevin From: Andy LoPresto Reply-To: Date: Monday, June 11, 2018 at 14:03 To: Subject: Re: [DISCUSS] Release candidate timeframe for Apache NiFi 1.7.0 Hi folks, With the

Re: NIFI URL

Thanks Tony and Chris for the help. I just synced up with Dev on HipChat. For those interested, he was running into this issue which was fixed in NiFi 1.5.0: https://issues.apache.org/jira/browse/NIFI-4640 Regards, Kevin On 6/3/18, 13:52, "Chris Herrera" wrote: Dev, Can you send

Re: [VOTE] Release Apache NiFi MiNiFi C++ 0.5.0

+1 (non-binding) I followed the steps in the helper guide and was able to verify the agent works as expected with a couple test flows that send data to NiFi over s2s. Most of my RC verification was done with the agent on Mac OS 10.12. A full build with tests passed on Ubuntu 16.04 for me. One

Re: [ANNOUNCE] New Apache NiFi Committer Sivaprasanna Sethuraman

Congrats, Sivaprasanna! On 6/5/18, 10:09, "Tony Kurc" wrote: On behalf of the Apache NiFI PMC, I am very pleased to announce that Sivaprasanna has accepted the PMC's invitation to become a committer on the Apache NiFi project. We greatly appreciate all of Sivaprasanna's hard work

Re: [ANNOUNCE] New NiFi PMC member Mike Thomsen

Congrats, Mike! On 6/6/18, 21:57, "Sivaprasanna" wrote: Congratulations, Mike! :) On Thu, Jun 7, 2018 at 4:54 AM, Otto Fowler wrote: > Congratulations! > > > On June 6, 2018 at 18:22:32, Tony Kurc (tk...@apache.org) wrote: > > NiFi community, > On

Re: Registry H2 to PostgreSQL migration

Hi Jagrut, I think this is configurable. How did you configure you nifi-registry.properties file? Thanks, Kevin From: Jagrut Sharma Sent: Saturday, June 23, 2018 2:43:33 PM To: dev@nifi.apache.org Subject: Registry H2 to PostgreSQL migration Hi - I performed

Re: [DISCUSS] Release Apache NiFi MiNiFi 0.5.0

Sounds good to me. Thanks, Aldrin. Get Outlook for iOS On Sun, Jun 24, 2018 at 3:04 PM -0400, "Andy LoPresto" wrote: +1, excited to get the new stuff

Re: [VOTE] Release Apache NiFi MiNiFi 0.5.0 RC2

+1, non-binding. Followed the steps in the release helper guide, verified the readme, ran a simple flow with s2s. Nice work everyone! Thanks for RM'ing this one Jeremy. Kevin On 7/1/18, 14:22, "Tony Kurc" wrote: +1 (binding) License + notice look good built without issue

Re: Multiple users or group as initial admin identity

Hi Fredrik and Bryan, I agree these changes would be fairly straightforward to make and could simplify deployment in some environments. I'll also add that while we look into this, in the meantime a workaround would be to continue to use the use the Initial Admin user, and have an automated

Re: [VOTE] Release Apache NiFi Registry 0.1.0

+1 (non-binding) - Verified sig, hashes, commit id - Verified full build with contib-check, integration-tests, and jsUnitTests - Checked README/NOTICE/LICENSE in source and target - Verified unsecured [1] [2] and secured (client cert, ldap) - Verified UI and REST API - Verified persistence of

Re: MINIFICPP-357 minifi-cpp Design decision: Flow Configuration v3 yml vs properties

Hi Andy, My preference would also be to keep the .yml scoped to flows, and keep instance config in a .properties file. When we get further along the C2 roadmap, both of these should be updatable via C2 interactions. Thanks, Kevin On 1/4/18, 16:04, "Joe Witt" wrote:

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

+1 (non-binding) - Verified hashes, sig, & commit id - Verified full build w/ contrib-check - Verified LICENSE, NOTICE, README present in source and build output - Verified target bin can run. - Verified integration with NiFi Registry - Verified behavior fixed in NIFI-4740 Nice work everyone!

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

Nice discussion on this thread. I'm also in favor of the long-term solution being publishing extension NARs to an extension registry (#3) and removing them from the NiFi convenience binary. A few thoughts that build upon what others have said: 1. Many decisions, such as the structure of the

Re: Nifi Registry problem

Hi Nitin, Your image attachment did not come through on the mailing list, at least for me. Can you please provide more information on the error you are encountering, for example the contents of nifi-registry-app.log when the error occurs. Thanks, Kevin From: Ullal Nitin

Re: Failed to execute goal org.apache.rat:apache-rat-plugin:0.11:check (default) on project nifi-poi-processors: Too many files with unapproved license

>From the output it appears to me that the maven rat plugin is failing to >identify >'nifi/nifi-nar-bundles/nifi-poi-bundle/nifi-poi-processors/src/test/resources/Unsupported.xls' > as a binary file. Do you know what version of the rat plugin your system has? >This is printed in the build

Re: [VOTE] Release Apache NiFi MiNiFi C++ 0.4.0 RC1

+1 (non-binding) Ran through the steps in the Release Helper Guide on Mac OS 10.12.6 using the source tar without issue. I'm ok with documenting the issue Andy C found on the source tarball download page as Marc P suggested. Thanks everyone! Kevin On 1/24/18, 01:36, "Aldrin Piri"

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

Hey Scott, I got a chance to take a look at your demo app. It's nice! I think your proposal is a good idea. A lot of effort went into creating this library for the use in NiFi Registry (awesome work on that!), and its pretty cool that something came out of it that can stand on its own to be

Re: [DISCUSS] Apache NiFi MiNiFi C++ 0.5.0

Hi Marc, Thanks for kicking off this discuss thread. I agree we should start planning the next release to get these new and improved capabilities into a stable version for users. Thanks! Kevin On 2/14/18, 13:42, "Marc" wrote: Hello Everyone, I wanted to

Re: [ANNOUNCE] New Apache NiFi Committer Kevin Doran

il.com> wrote: On behalf of the Apache NiFi PMC, I am very pleased to announce that Kevin Doran has accepted the PMC's invitation to become a committer on the Apache NiFi project. We greatly appreciate all of Kevin's hard work and generous contributions to the project. We loo

Re: Apache NiFi 1.7.0 RC1 Release Helper Guide

Hi Mike, These values are in the VOTE email:https://lists.apache.org/thread.html/d8bfef873317c5f681a5deb226d9dd9483aec56a7abc9a72090cb570@ Cheers,Kevin On Wed, Jun 20, 2018 at 6:55 AM -0700, "Mike Thomsen"

Re: Upgrading NiFi Registry

Thanks Mark and Bryan. I will add a NiFi Registry 0.1 -> 0.2 migration guide to include these steps as part of updating the site with news of the new release. Thanks, Kevin From: Mark Bean Sent: Wednesday, June 20, 2018 8:53:39 AM To: dev@nifi.apache.org

Re: [VOTE] Release Apache NiFi Registry 0.2.0

at 6:26 PM Kevin Doran wrote: > Hello, > > I am pleased to call this vote for the source release of Apache NiFi > Registry 0.2.0. > > The source zip, including signatures, digests, etc. can be found at: > > https://dist.apache.org/repo

[RESULT][VOTE] Release Apache NiFi Registry 0.2.0

Apache NiFi Community, I am pleased to announce that the 0.2.0 release of Apache NiFi Registry passes with: 9 +1 (binding) votes 3 +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:

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 < > ottobackwa...@gmail.com > > > > > > > > wrote: > > > > > > > > > > > Congratula

Re: Comparing NiFi API versions between releases

Hi Jagrut, Are you referring to the REST API or the public Java interfaces and classes? As a general note, NiFi versions follow semantic versioning [1] guidelines, so for external-facing APIs (both Java and REST), there may be additions or non-breaking changes across minor versions, but there

Re: How does logging level get set?

Hi, Logging level is set in logback.xml. To change the logging level for a given logger/package/class, you must modify that file. See [1] for more details. In your code example, you are creating the logger correctly using the LoggerFactory. All NiFi Frameworks and extensions use the slf4j API,

Re: [VOTE] Establish Fluid Design System, a sub-project of Apache NiFi

+1 (non-binding) On 3/12/18, 09:01, "Matt Gilman" wrote: +1 On Sun, Mar 11, 2018 at 11:40 PM, Koji Kawamura wrote: > +1 > > On Mon, Mar 12, 2018 at 3:10 AM, Matt Burgess > wrote:

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

+1 (non-binding) Release this package as nifi-1.6.0 Comments: - sig and hashes look good - ran a simple flow, saving/loading from Registry - full build w/tests passed, but it took two attempts. First time failed @ nifi-ambari-reporting-task due to a test failure: [ERROR] Errors: [ERROR]

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

+1 I ran through the steps in the release helper guide and everything looks good. Thanks for handling RM duties, Joe. --Kevin On 3/26/18, 23:34, "Joe Witt" wrote: Hello, I am pleased to be calling this vote for the source release of Apache NiFi

Re: [ANNOUNCE] New Apache NiFi Committer Mike Thomsen

Congrats, Mike! On 3/21/18, 09:42, "Tony Kurc" wrote: On behalf of the Apache NiFI PMC, I am very pleased to announce that Mike has accepted the PMC's invitation to become a committer on the Apache NiFi project. We greatly appreciate all of Mike's hard work and

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

I like NiFi Design System. A bit "boring" perhaps, but probably the most self-descriptive project name for newcomers. I like Fluid Design System as well if the intent is to be more generic, indicating that it is not intended just for NiFi projects but can be utilized anywhere (but "fluid" has

Re: [DISCUSS] MiNiFi Flow Designer

Aldrin, Thanks a lot for taking the time to write up such a detailed and well thought out proposal. I really like the idea of publishing flows to NiFi Registry that then get deployed to MiNiFi agents via the C2 Server. I don't have much to add there, and I think that you've identified one of

Re: Upgrading NiFi Registry

n Wed, Jun 20, 2018 at 11:57 AM, Kevin Doran wrote: > > Thanks Mark and Bryan. I will add a NiFi Registry 0.1 -> 0.2 migration > guide to include these steps as part of updating the site with news of the > new release. > > > > Thanks, > > Kev

Re: Upgrading NiFi Registry

as just my hastiness or if there is something else at play. On Thu, Jun 28, 2018 at 2:33 PM Kevin Doran wrote: > Thanks Aldrin! That sequence makes sense to me and should result in a > clean copy of the H2 Database. Mike, you're probably aware of this, but you > wil

Re: Upgrading NiFi Registry

f the GitFlow option at this point? That was particularly attractive as a storage solution because it should make it much easier to export everything from our dev team to our end users. Thanks, Mike On Thu, Jun 28, 2018 at 1:28 PM Kevin Doran wrote: > Mike,

Re: Upgrading NiFi Registry

sions of 0.1.0 and 0.2.0 and it seemed to work as anticipated. Let us know how it goes. On Thu, Jun 28, 2018 at 1:52 PM Kevin Doran wrote: > Oh right. My mistake. Not sure if there is a way to stop the nifi registry > process without stopping the con

Re: NiFi documentation source files?

HI Mark, As Apache NiFi is an open source project, you are welcome to all of the source files, including the documentation, available here [1] and mirrored to github as well [2]. The documentation source, written in asciidoc, is in the nifi-docs module of the project [3]. [1]

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

+1 (binding) Ran through the steps in the helper guide. Ran a test by Running NiFi, connecting with registry, and versioning/importing/running flows. Thanks for RM'ing this release, Jeff! Kevin On 10/25/18, 12:48, "Joe Witt" wrote: +1 (binding) Did the usual checks. Ran into

Re: API to get all Policies

Hi Lars, I think as long as the following are true (it sounds like they are from what you have looked at): 1. the proposed endpoint does not require adding any additional Authorizable or policy to protect, and 2. the proposed endpoint does not expose any information that the authenticated

Apache NiFi Registry 0.3.0 RC1 Release Helper Guide

Hello Apache NiFi community, Please find the associated guidance to help those interested in validating/verifying the Apache NiFi Registry release so they can vote. # Download latest KEYS file: https://dist.apache.org/repos/dist/dev/nifi/KEYS # Import keys file: gpg --import KEYS # [optional]

[VOTE] Release Apache NiFi Registry 0.3.0

Hello, I am pleased to call this vote for the source release of Apache NiFi Registry 0.3.0. The source zip, including signatures, digests, etc. can be found at: https://dist.apache.org/repos/dist/dev/nifi/nifi-registry/nifi-registry-0.3.0/ The Git tag is nifi-registry-0.3.0-RC1 The Git commit

[ANNOUNCE] Apache NiFi Registry 0.3.0 Release

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

Re: [VOTE] Release Apache NiFi Registry 0.3.0

. > > Thanks for RM'ing Kevin! > > On Sat, Sep 22, 2018 at 9:54 AM Kevin Doran wrote: > > > Hello, > > > > I am pleased to call this vote for the source release of Apache NiFi > > Registry 0.3.0. > > > > The source zip, including signatures, digests, etc.

[RESULT][VOTE] Release Apache NiFi Registry 0.3.0

Apache NiFi Community, I am pleased to announce that the nifi-registry-0.3.0 release of Apache NiFi Registry passes with 11 +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 vote thread:

Re: [ANNOUNCE] New Apache NiFi Committer Ed Berezitsky

Congrats, Ed! Thanks for all the hard work! On 1/2/19, 22:32, "Sivaprasanna" wrote: Congratulations, Ed! - Sivaprasanna On Thu, 3 Jan 2019 at 8:12 AM, Joe Witt wrote: > Congrats and thanks Ed! > > On Wed, Jan 2, 2019 at 9:36 PM Tony Kurc wrote:

Re: [ANNOUNCE] New Apache NiFi Committer Nathan Gough

Congrats, Nathan! Thanks for all the contributions to the project! On 1/2/19, 22:33, "Sivaprasanna" wrote: Congratulations, Nathan! On Thu, 3 Jan 2019 at 8:12 AM, Joe Witt wrote: > Congrats and thanks Nathan! > > On Wed, Jan 2, 2019 at 9:30 PM Tony Kurc wrote:

Re: [DISCUSS] Early, voluntary relocation to GitBox

+1 On 12/7/18, 15:17, "Andy LoPresto" wrote: +1. Andy LoPresto alopre...@apache.org alopresto.apa...@gmail.com PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4 BACE 3C6E F65B 2F7D EF69 > On Dec 7, 2018, at 11:11 AM, Aldrin Piri wrote: > > Hey folks, >

Re: API to get all Policies

but I also agree that in this case it's probably not worth the hassle. I'll go ahead and create a Jira. I plan on providing a patch but not sure when I'll get to it. Cheers, Lars On Fri, Nov 9, 2018 at 6:38 PM Kevin Doran wrote: > Hi Lars, &g

Re: Nifi creating directories on start?

Hi Arun, Those are directories used by NiFi or its bootstrap service to store state. NiFi creates several directories and files on disk to save state while running, so it is expected the run-as-user has write access to the NiFi home directory and its sub-directories. Hope this helps, Kevin

Re: [DISCUSS] NiFi and Java 11

Jeff, Thanks for all your work on this and for explaining the path forward. I also support this proposal. I suggest we take the same basic approach for NiFi Registry. That is: - For the current NiFi Registry 0.x line, we maintain Java 8 and 11 build compatibility - We perform Java 8 builds

Re: Reg:Nifi registery

Hi Prashanth, By default, NiFi Registry stores all data (flows, metadata, etc) in sub directories of its home directory (the install dir, which has sub dirs such as /conf, /lib, and /bin), so as long as you are taking regular backups of that directory you should be able to restore from a backup.

Re: [DISCUSS] Closing in on a NiFi Registry 0.4.0 release?

Hi Ryan, Bryan can speak more to this than I can, but, yes, providing the experience you describe is the eventual goal! Aside from the NiFi Extension Registry support though (the initial bits of which is what Bryan is referring to in 0.4.0), getting the full, streamlined experience in NiFi will

Re: Unable to use Github as flowPersistenceProvider for NiFi Registry

What platform are you running on? I've heard of some issues when trying to use the GitFLowPersistenceProvider on Windows. Technically, only Linux is a supported platform for NiFi Registry. On Wed, Mar 6, 2019 at 7:57 AM Denes Arvay wrote: > > Hi Satwik, > > Don't you have a firewall running

Re: [DISCUSS] Apache NiFi MiNiFi C++ 0.6.0

Wow, that list of features is impressive, and certainly I agree it would be great to get them all in a release. Thanks for kicking it off, Marc! Regards, Kevin On Tue, Mar 5, 2019 at 8:41 AM Marc Parisi wrote: > > Hello everyone, > I wanted to discuss releasing Apache NiFi MiNiFi C++ 0.6.0 in

Re: Docker build broken for me in 1.9.1RC2

Agree we should probably update master to use the latest plugin. For what it's worth, on the RC, I ran this and both completed fine: mvn -T 2 install -Pcontrib-check,include-grpc,include-atlas mvn install -Pdocker -DskiptTests -pl nifi-docker/dockermaven I am logged into dockerhub. On

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

+1 (binding) Ran through the steps in the release helper guide and verified that NIFI-6108 is fixed in this release. Thanks again for RM'ing, Joe. Kevin On Thu, Mar 14, 2019 at 11:41 AM Laszlo Horvath wrote: > > +1 (non-binding) > > - Verified signature > - Verified hashes > - Verified the

Re: [VOTE] Release Apache NiFi MiNiFi C++ 0.6.0 (RC2)

+1, binding - verified build on Mac OS X 10.14 and Alpine Linux (using docker build) - exercised various new features including JNI processors and CoAP support I did observe a minor issue using the bootstrap script on Mac [1] for which I submitted [2]. All in all, really great release --

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

+1 (binding) - Verified by following the steps in the release helper. - Created a docker image with the resulting binary and verified Registry integration using apache/nifi-registry:0.3.0 docker container. - Verified bugfix for NIFI-5950 in the rc Everything worked great! Thanks to everyone who

Re: Contributions and getting started

Hi Ryan, Welcome to the Apache NiFi community! It's great to hear that you're interested in contributing to the project. In addition to what Andy said, here are a couple notes that might help:  - The ASF git repo URL you mentioned [1] is an old URL. The project recently moved to gitbox [2] /

Re: [VOTE] Release Apache NiFi Registry 0.4.0

+1 (binding) Followed the steps in the release helper's guide. One minor thing I noticed was that a few dates in the nifi-registry-assembly NOTICE file need to be updated (the source NOTICE looks good though). There are a ton of great improvements in this release. Nice work everyone, and thanks

Re: [EXT] [discuss] Splitting NiFi framework and extension repos and releases

I am also in favor of splitting the nifi maven project up into smaller projects with independent release cycles in order to decouple development at well defined boundaries/interfaces and also to facilitate code reuse. In anticipation of eventually working towards a NiFi 2.0 that introduces bigger

Re: Maven artifact GPG signing

Hi Andy, Thanks for bringing this up and looking into the mechanics of how to get it working. I am a +1 for signing our maven artifacts. Thanks, Kevin On Wed, May 29, 2019 at 6:09 PM Andy LoPresto wrote: > > Hi folks, > > I am writing to propose updating our release process to include signing

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

Congrats, Peter! Well deserved. On Thu, May 30, 2019 at 1:22 PM Andy LoPresto wrote: > > Congratulations Peter. > > Andy LoPresto > alopre...@apache.org > alopresto.apa...@gmail.com > PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4 BACE 3C6E F65B 2F7D EF69 > > > On May 30, 2019, at 8:22 AM, Joe Witt

Re: [EXT] Re: GitHub Stuff

Yep, I support these suggestions. Setting up GPG does have a learning curve for folks that haven't done it before, but I think our community would be helpful in assisting folks on the mailing list and Apache NiFi Slack where they run into trouble. It's a good practice to learn and once setup

Re: [ANNOUNCE] New Apache NiFi Committer Arpad Boda

Congrats, Arpad! Thanks for all the contributions to MiNiFi! On Thu, May 23, 2019 at 3:59 PM Andrew Lim wrote: > > Congrats Arpad! > > > On May 23, 2019, at 9:23 AM, Aldrin Piri wrote: > > > > On behalf of the Apache NiFI PMC, I am very pleased to announce that Arpad > > has accepted the PMC's

Re: Support Gradle for building NAR

Something to keep in mind is that the master branch of the nifi-maven plugin has been updated recently to include additional logic for generating and including metadata information in the resulting NAR. This is a stepping stone to adding support for hosting NAR extension bundles in NiFi Registry.

  1   2   3   >