[
https://issues.apache.org/jira/browse/NIFI-259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15122770#comment-15122770
]
Mark Payne commented on NIFI-259:
---------------------------------
The ZK logs should show up in the nifi-app logs. I have been seeing them there.
ZK in standalone mode is not something that we support. I didn't make it error
out if it is configured, just because I figured that admins may have a reason
to take a node out of a cluster temporarily and stand it up as a standalone and
having to go in and disable that seemed unnecessary. Instead, it will simply
use the Local State Provider in all cases. However, if you think that it is
less confusing to produce an error in this case, then I am totally okay with
that as well.
> Framework should offer Processors/extensions a way to manage simple state
> -------------------------------------------------------------------------
>
> Key: NIFI-259
> URL: https://issues.apache.org/jira/browse/NIFI-259
> Project: Apache NiFi
> Issue Type: Sub-task
> Components: Core Framework
> Reporter: Joseph Witt
> Assignee: Mark Payne
> Fix For: 0.5.0
>
> Attachments: error-message.png
>
>
> It is not uncommon for processors to need managed state which persists
> across restarts. One good example of this is the GetHTTP processor which
> needs to save state of the last cache/e-tag information it received from the
> server it interacts with so that it can avoid constantly pulling an unchanged
> resource.
> Rather than making processors roll their own persistant state management
> perhaps we can offer something to them via the ProcessContext which will
> allow them to save simple primitive values and limited length Strings which
> are local to that node and which are local to that processor only.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
