[ANNOUNCE] Apache NiFi MiNiFi 0.0.1 release

Hello! The Apache NiFi team would like to announce the release of Apache NiFi - MiNiFi 0.0.1. MiNiFi is a subproject of Apache NiFi. MiNiFi provides a complementary data collection approach that supplements the core tenets of NiFi in dataflow management, focusing on the collection of data at

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

+1 (binding). On Sun, Jul 10, 2016 at 1:26 AM, Andy LoPresto wrote: > +1 (binding) > > Verified key signature and all hash digests. > > Verified build with contrib-check. > > Deployed in a single, standalone, unsecured instance and a secure 2-node > cluster. > > Andy

Re: State sharing

Thanks Bryan. Would be nice if we get support for state sharing across diffrent processors in the future. -Sumo Sent from my iPhone > On Jul 10, 2016, at 7:39 PM, Bryan Bende wrote: > > Sumo, > > Two different processor instances (different UUIDs) can not share state >

Re: State sharing

Andrew, If I use cluster mode, if one processor writes state, a diffrent processor can read it ? I understand that same processor on multiple nodes in the cluster can share state. Thanks Sumo Sent from my iPhone > On Jul 10, 2016, at 7:23 PM, Andrew Grande wrote: > >

Re: State sharing

Sumo, Two different processor instances (different UUIDs) can not share state that is stored through the state manager. For something like this you would likely use the distributed map cache. As Andrew mentioned, the state is accessible across the cluster, so a given processor can access the

Re: State sharing

Sumo, IIRC there's a node one selects when setting state. If you invoke with a cluster mode, the state will be set to a ZK by default. Otherwise just local to this processor node. Andrew On Sun, Jul 10, 2016, 10:17 PM Sumanth Chinthagunta wrote: > If I set state from one

State sharing

If I set state from one ExecuteScript processor via stateManager , can I access same state from other processor ? Thanks Sumo Sent from my iPhone