[
https://issues.apache.org/jira/browse/NIFI-259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15131188#comment-15131188
]
ASF subversion and git services commented on NIFI-259:
------------------------------------------------------
Commit 447e401912100ab9ed73d442e1e8c0c0bb229725 in nifi's branch
refs/heads/NIFI-259 from [~aldrin]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=447e401 ]
NIFI-259: Extending the StateProvider interface to provide a getSupportedScopes
method and implemented this based on the capabilities of each of its
implementations. Used supported scope to evaluated configurations at startup
and prevent issues when trying to make use of state
> 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)
