[
https://issues.apache.org/jira/browse/NIFI-259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14552236#comment-14552236
]
Mark Payne commented on NIFI-259:
---------------------------------
I think we need to remove the concept of "which are local to that node". This
needs to be capable of handling distributed state across the cluster, as well.
The ListHDFS processor does a lot of work to do this, and it should be the
responsibility of the Framework. Though this concept could be moved into a
different ticket, but I think that if we are going to introduce the concept of
state management it should be done together so that we don't then have to
change the API to allow for local vs. clustered management
> 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
>
> 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)
