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

+1, binding Went through the release helper guide and all looks good to me AFAICT. I merged the PR from Andy and set the fix version to 0.2.0. (could be a good idea to ask infra for a dedicated JIRA so we don't mix things regarding version numbers?) Congrats on this first release and thanks to

Re: LookupService + flowfile attributes

I think the only services that won't break if you merge the variables are the ones that use only mandatory keys. Ones like MongoDBLookupService will simply take the entire lookup coordinate map and turn it into a query. I don't think there's an elegant solution to allow the service to pick and

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

+1 * Stepped through the release guide to verify the sig, hashes, and commit ID * Checked for readme, notice, and license in source and target * Checked for the package version update changes * Ran the demo app – seems to be a slight delay initially loading up but all looks good Thanks for all

Re: Custom Processor Bundle Contribution

Thanks Pierre for the reply. I will check and follow the procedure. Regards, Prashanth V On Tue, Jun 12, 2018 at 1:01 PM, Pierre Villard wrote: > Hi Prashanth, > > First step is to create a JIRA describing the new feature you want to > contribute [1]. > Then you can have a look at the

Re: LookupService + flowfile attributes

Hi Mike, I'm still not sure which is better, separating the variables or containing all values. I wrote a comment so that we can keep the discussion there. https://github.com/apache/nifi/pull/2777#issuecomment-396512384 Thanks, Koji On Tue, Jun 12, 2018 at 1:56 AM, Mike Thomsen wrote: > Koji,

Re: Question on Docker module

Hi, following up on my last email I've implemented both changes I was referring to. First I've added the the same integration tests, that dockermaven already uses to cover the dockerhub image as well. Unfortunately for this I had to use the latest public artifact (1.6.0) since only that is

Fwd: Custom Processor Bundle Contribution

Hi Team, I created network related custom processor and would like to contribute it to NiFi source. I want to know the procedure to contribute to NiFi. Please provide me the detailed guidelines.. -- *With regards,* Prashanth V

Re: Contributing Apache-2.0 licensed code from a 3rd party into NiFi

Peter, Broadly speaking there are a few ways code becomes part of the project as I understand it. 1) An author, an individual contributor, provides a source code contribution to the Apache project that is an original work of that author. This could be a patch attached to a JIRA or as a pull

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

+1, binding comments: * source commit looks correct * hashes and signature looked good * build was successful * LICENSE and NOTICE looks good. There was a small error referring to Registry as being ASLv2 which should be ALv2. A PR has been created to correct this:

Re: Unable to install Apachi nifi on my unix box

What error do you get when you run it? Please share it over here. BTW, which version of Apache NiFi are you using? Thanks, Sivaprasanna On Tue, Jun 12, 2018 at 7:24 PM, Srinivasa Rao Potla < srinivasarao.po...@infosys.com> wrote: > Hi Team, > > > > I have unable to run the below step , I have

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

Unable to install Apachi nifi on my unix box

Hi Team, I have unable to run the below step , I have downloaded the as per github steps . But unable to start the below step to start the apache nifi ./bin/nifi.sh start [cid:image001.png@01D40283.03881BD0] Regards, Srinivasarao Potla +91 8886210 www.infosys.com

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

+1 binding Ran through helper guide. Verified signatures, hashes, build, etc. Version strings look better with this RC. Provided other feedback regarding improvements to the demo app during RC1. Thanks for RMing this Scott! Matt On Tue, Jun 12, 2018 at 8:28 AM, Rob Moran wrote: > +1 > > *

Re: Unable to install Apachi nifi on my unix box

Srinivasarao, I think you attempted to attach an image with the error which did not make it through to the email list. Tony On Tue, Jun 12, 2018 at 10:03 AM, Sivaprasanna wrote: > What error do you get when you run it? Please share it over here. BTW, > which version of Apache NiFi are you

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

Aldrin, Yes we do need INFRA to help us delete the rel/nifi-registry-0.1.0. The node_modules for the gh-pages branch, however, have been purposely committed to support the github.io demo . On Tue, Jun 12, 2018 at 10:30 AM Kevin Doran wrote: > +1