[
https://issues.apache.org/jira/browse/NIFI-259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15115452#comment-15115452
]
Mark Payne commented on NIFI-259:
---------------------------------
One thing that we may want to consider adding to this in the future is the
notion of a 'write delay' when setting state. For example, instead of just
doing:
{code}
setState(Map<String, String> state, Scope scope);
{code}
We could also have:
{code}
setState(Map<String, String> state, Scope scope, long writeDelay, TimeUnit
writeDelayUnits);
{code}
This would allow a developer to trade off durability for performance if it
makes sense to do so in the context of the Processor.
> 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
>
>
> 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)
