I expect that in the future I’ll need something a little more sophisticated but for now my problem is very simple: I want to be able to trigger an alert (only once) when an attribute in an incoming stream, for instance, goes over a predefined threshold. The Processor should then trigger (only once again) another trigger when the signal goes back to normal (below threshold). Basically a RouteByAttribute but with memory.
Thanks Claudio On 2/24/16, 8:56 PM, "Joe Witt" <[email protected]> wrote: >Claudio > >Hello there and welcome to the nifi community. There are some >processors available now that allow you to store values in distributed >(across the cluster) maps and to retrieve them. And now within >processors there is the ability interact with state management >features built into the framework. So the basic pieces are there. I >would like to better understand the idea though because it may be even >more straight forward. > >Where does the state or signal come from that would prompt you to >store a value away? And is this source/signal separate from the feed >of data you'd like to tag with this value? > >For example, we have the UpdateAttribute processor which can be used >to tag attributes onto flow files going by. You can of course simply >call the rest api to change the tag being applied as needed and that >can be done by whatever the signal/source is potentially. > >Thanks >Joe > >On Wed, Feb 24, 2016 at 11:49 PM, Claudio Caldato ><[email protected]> wrote: >> >> I need to be able to store a simple value (it can be true/false) in the >> processor across messages, basically I need a processor with a local state >> (set of properties) that I can use to set the value of properties on output >> messages >> >> Can it be done or do I need to build a custom processor? >> >> Thanks >> Claudio >>
