Re: [ANNOUNCE] New Apache NiFi PMC Member - Koji Kawamura

Congrats Koji! Thanks for all the great contributions and docs to accompany. On Fri, May 26, 2017 at 11:39 PM, Yolanda Davis wrote: > Congratulations Koji! > > Sent from my iPhone > > > On May 26, 2017, at 10:58 PM, Andy LoPresto > wrote: > > >

Re: [ANNOUNCE] New Apache NiFi PMC Member - Koji Kawamura

Congratulations Koji! Sent from my iPhone > On May 26, 2017, at 10:58 PM, Andy LoPresto wrote: > > Congratulations Koji. For anyone not familiar with some of his greatest hits, > it’s not just the (impressive) code contributions like the Wait & Notify > processors and

Re: [ANNOUNCE] New Apache NiFi PMC Member - Koji Kawamura

Congratulations Koji. For anyone not familiar with some of his greatest hits, it’s not just the (impressive) code contributions like the Wait & Notify processors and massive Site-to-site refactoring, but his detailed blog posts explaining complex topics very clearly. Well-deserved. Andy

Re: [ANNOUNCE] New Apache NiFi PMC Member - Koji Kawamura

Congrats Koji and thanks for all your efforts and contributions to the community. I remember how cool it was to read this https://blog.couchbase.com/apache-nifi-and-couchbase-server/ And your blogs and outreach have just kept getting better! Thanks Joe On Fri, May 26, 2017 at 9:09 PM, Tony

[ANNOUNCE] New Apache NiFi PMC Member - Koji Kawamura

On behalf of the Apache NiFi PMC, I am pleased to announce that Koji Kawamura has accepted the PMC's invitation to join the Apache NiFi PMC. We greatly appreciate all of Koji's hard work and generous contributions to the project. We look forward to continued involvement in the project. Koji has

Re: Zero-Downtime Deployments with Component Versioning

Bryan, Our current NiFi cluster has a complex flow with dozens of unique custom NARs. It would take hours of painstaking patience to identify every location where a custom component needs upgrading. It would be helpful to list the version in the summary table. At least that way, I could

Re: Setting basic NiFi network problem

Hi Xophos, You need to ensure that all the ports are different if you're running the instances on a single machine. That includes the http(s) port. Your operating system will not let multiple processes bind to the same ip address and port. Relevant portion of the exception:

Re: Setting basic NiFi network problem

Thanks for the help so far but i am now getting stuck i have this error form the log file and i am not sure how to fix i been trying to look it up online but there no solution insight maybe you've seen it before. The Errors 2017-05-26 14:54:09,495 ERROR [Leader Election Notification Thread-1]

Re: Zero-Downtime Deployments with Component Versioning

Hi Richard, I believe this is currently expected behavior, meaning that rolling deployments are not supported when changes to NARs are being made. There are two main issues... The first is that if nodes are running different versions of the framework NAR, they could potentially be running

Zero-Downtime Deployments with Component Versioning

Dear dev, I recently upgraded to NiFi version 1.2.0. In doing so, I lost the ability to perform rolling upgrades on my 6-node cluster due to component versioning, i.e. MissingBundleExceptions. My previous deployment steps are listed below. My question for the devs is this: what is the best

Re: Connecting Nifi 1.2.0 with Google Cloud Storage issue

Hi James, Yes, 'gsutil ls' lists the bucket fine when I run it from the instance. The service account was created and associated with the Storage Object Viewer and the Storage Object Creator roles. I have also added the role to the acl of the bucket (Bucket Permissions) and objects in the

Re: nifi-jms-processor not closing connection properly in "primary node only" execution mode

Dominik, Sorry for the delayed response... I think the issue is that currently the processor is started/schedule on all nodes, regardless of whether it is primary or not, but then only the instance on the primary node is triggered to run. So when the primary node changes from node1 to node2,

Re: Connecting Nifi 1.2.0 with Google Cloud Storage issue

Martin, If you ran "gsutil ls" against the bucket from the instance using the service account, is it able to list the bucket? Can you describe a bit more about how the service account's access to the bucket was configured? Is it added to one of the project roles, explicitly granted on the

difficulty killing NiFi w/ nifi.sh stop under 1.2.0 now vs. 1.1.2 when run as systemd service

Greetings, I’m hoping to upgrade the my software team’s baseline to use NiFi 1.2.0. I’m having trouble w/ a particular situation of trying to take nifi down. Prior to this version, I’ve been able to use the nifi.sh script w/o sudo rights to kill nifi when it has been brought up by a service

Connecting Nifi 1.2.0 with Google Cloud Storage issue

Hi all, I have a Google Compute instance with a service account configured. I have installed Nifi 1.2.0 on it. In the Nifi UI I am describing a flow. The first processor is a ListGCSBucket processor. It is pointing to a bucket for which the service account is added as owner and I am not