[
https://issues.apache.org/jira/browse/NIFI-259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15131185#comment-15131185
]
ASF subversion and git services commented on NIFI-259:
------------------------------------------------------
Commit 72c8467b9f2d64d0d441331851dc23f25e927736 in nifi's branch
refs/heads/NIFI-259 from [~mcgilman]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=72c8467 ]
NIFI-259:
- Addressing typo in documentation.
- Minor tweaks to admin guide.
- Adding support to stand up a ZooKeeperServer when a quorum peer is not
distributed (ie supporting both embedded standalone and cluster).
Signed-off-by: Aldrin Piri <[email protected]>
> 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)
