Re: [DISCUSS] MiNiFi Releases

agreed. will try to do minifi java release validation tomorrow or fri morn. thanks aldrin! On Jan 17, 2018 8:50 PM, "Tony Kurc" wrote: > I like what you have to say > > On Jan 16, 2018 9:17 AM, "Aldrin Piri" wrote: > > > Hey folks, > > > > With the

Re: [DISCUSS] MiNiFi Releases

I like what you have to say On Jan 16, 2018 9:17 AM, "Aldrin Piri" wrote: > Hey folks, > > With the release of NiFi 1.5 we have a current gap in the typical flow > performed in taking a template with an RPG to connect from a MiNiFi > instance to NiFi as discovered in

Re: Nifi upgrade - patch

Hi Mike , Thank you for the reply. Our admin installed Nifi using the binaries available on the nifi website and unfortunately we don't have a git client setup on the Linux cluster, Nor do i have the rights or permission to setup one. Would it be possible for your to provide the Nar files which

Re: Nifi upgrade - patch

On 2018-01-17 22:41, Mike Thomsen wrote: > Clone my NIFI-3538 branch referenced in the pull request and build all of > the HBase modules. There's three: > > 1. A service API in the services folder. > 2. A service implementation in the services holder. > 3. The

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

> On 18 Jan 2018, at 03:07, Matt Burgess wrote: > > BTW, talking about mixin inheritance, shared dependencies, improved > classloading, and module repositories, I feel like OSGi is the > elephant in the room. I can see perfectly good reasons NOT to move to > an

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

> On 18 Jan 2018, at 03:05, Matt Burgess wrote: > > - Some NiFi installs will be located on systems that cannot contact an > outside (or any external) repository. When we consider NAR > repositories, we should consider providing a repo-to-go or something > of that sort.

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

I'm glad to see the discussion of this topic. I have nothing material to add apart the caution that making NiFi too hard to install (it has always been super easy--especially important for non-engineer folk) will detract from my ability to recommend it. If it becomes a multistep action, adding

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

absolutely yes Sumanth - that is what the extension registry would enable. There are lots of great discussion points and feedback in this thread. I'll try to summarize in a table of pros/cons. We'll want to offer a range of these I suspect. Thanks Joe On Wed, Jan 17, 2018 at 11:21 AM, Sumanth

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

Just an idea, can we also manger Nar, custom Nars in NiFi Repository and let fresh NiFi installers to add required nars and their dependencies on the fly vi NiFi UI ? -Sumanth > On Jan 17, 2018, at 8:05 AM, Matt Burgess wrote: > > I'd like to echo many of the comments

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

BTW, talking about mixin inheritance, shared dependencies, improved classloading, and module repositories, I feel like OSGi is the elephant in the room. I can see perfectly good reasons NOT to move to an OSGi-backed architecture, but it does feel like we'd end up implementing many of the same

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

I'd like to echo many of the comments / discussion points here, including the extension registry (#3), NAR packs, and mixins. A couple of additional comments and caveats: NAR package management: - Grouping NAR packs based on functionality (Hadoop, RDBMS, etc.) is a good first start but it still

Apache NiFi MiNiFi 0.4.0 RC1 Release Helper Guide

Hello Apache NiFi community, Please find the associated guidance to help those interested in validating/verifying the 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] Clear out local

[VOTE] Release Apache NiFi MiNiFi 0.4.0

Hello, I am pleased to call this vote for the source release of Apache NiFi MiNiFi minifi-0.4.0. The source zip, including signatures, digests, etc. can be found at: https://repository.apache.org/content/repositories/orgapachenifi-1118 The Git tag is nifi-minifi-0.4.0-RC1 The Git commit ID is

Re: Nifi upgrade - patch

Clone my NIFI-3538 branch referenced in the pull request and build all of the HBase modules. There's three: 1. A service API in the services folder. 2. A service implementation in the services holder. 3. The nifi-hbase-bundle package (has a processor and nar project) in the nifi-nar-bundles

Nifi upgrade - patch

New feature request Jira for deleting a Hbase row using Nifi processor has been marked as 'Patch available' ( https://issues.apache.org/jira/browse/NIFI-3538) . There is a github link for the pull request mentioned in the ticket as well. Can some one tell how to add this to our instance of Nifi so