the processor again?
>
> --Peter
>
> -Original Message-
> From: Joe Witt [mailto:joe.w...@gmail.com]
> Sent: Monday, August 15, 2016 2:06 PM
> To: dev@nifi.apache.org
> Subject: Re: Externally update processor State
>
> Peter,
>
> Ok understood. I feel like the Qu
-Original Message-
From: Joe Witt [mailto:joe.w...@gmail.com]
Sent: Monday, August 15, 2016 2:06 PM
To: dev@nifi.apache.org
Subject: Re: Externally update processor State
Peter,
Ok understood. I feel like the QueryDatabaseTable processor should have a
property for exactly this. And there is
o the necessary value, and then start the processor back up as
> part of their resolution process.
>
> Regards,
> Peter
>
> -Original Message-
> From: Joe Witt [mailto:joe.w...@gmail.com]
> Sent: Monday, August 15, 2016 1:51 PM
> To: dev@nifi.apache.org
> S
eir
resolution process.
Regards,
Peter
-Original Message-
From: Joe Witt [mailto:joe.w...@gmail.com]
Sent: Monday, August 15, 2016 1:51 PM
To: dev@nifi.apache.org
Subject: Re: Externally update processor State
Peter,
The state management function the is built-in is to allow processors t
Peter,
The state management function the is built-in is to allow processors
to set/interact with their own managed state. We did not intend for
that to be something someone external to the processor could interact
with directly. Rather, that is what properties are expected to be
used for.
So fa
I'm looking for a way to externally update a processors state, preferably
through an API call and then at some point the existing State viewer with the
clear button. From digging through the code base I couldn't find an exposed API
that would allow for state modification; only a state clearing.
