[
https://issues.apache.org/jira/browse/NIFI-259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15094601#comment-15094601
]
Matt Gilman commented on NIFI-259:
----------------------------------
Simply showing the state entries for a specific component may be too low level
for most users without knowing why the component is persisting state in the
first place. I would like to suggest possibly introducing a new Annotation that
could be specified on a component that indicates that it utilizes this state
feature, it's scope, and why.
1) Unit tests could enforce that Components that interact with this API have
this Annotation.
2) The UI can use the presence of this Annotation to toggle the View State
action.
3) The UI can use the description specified in the Annotation to provide more
context regarding its state to the user.
> 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)
